Originally Posted by Lanchon
i think he wants those as separate commits. and i think you can abandon your own change yourself in gerrit.
Yes, although in this case, the changeID for the "squashed" commit could have been preserved and used for the final commit in the chain. Yes, you can alter dependency chains for existing commits.
Yup. Only issue I have is that for the upstream patches, you added "smdk4412" to the commits even though they're just plain old upstream cherry-picks (unless zeitferne did this too???)
It's easy enough to fix this, I can edit the commit messages tonight.
Originally Posted by GidiK
I have made a build (omni-4.4, i9100) with all 13 patches applied. I reconfirmed that I could reproduce the fuse bug with a recent nightly and ran the exact same test with the new build. And good news: the bug is gone! So as far as I am concerned, they are good to go.
The test I did:
tar c Movies > /dev/null
while in another terminal window monitor progress with:
iostat -k 5
On the recent nightly it would get stuck the moment the screen went off.
Thanks to all involved in finding this solution!
Based on your input, I'll be ninjamerging these without personally testing them tonight, can you go into Gerrit and +1 them as confirmation?