https://bugzilla.suse.com/show_bug.cgi?id=1164503 https://bugzilla.suse.com/show_bug.cgi?id=1164503#c35 --- Comment #35 from Filipe Manana <fdmanana@suse.com> --- (In reply to Fabian Vogt from comment #34)

(In reply to Filipe Manana from comment #33)

...

...

What's the target for a kernel submission to TW?

What do you mean? When can I merge them to the branch origin/stable?

If that's the question, than at any time. I should be sending the patches upstream tomorrow or monday (had to do some changes to the change logs, and add another patch to the series for a different but related problem).

Usually for tumbleweed I wait for them to go upstream first and then automatically merged to the stable branch, unless it's something very serious that is being hit frequently by users. In this last case I add them manually even before hitting Linus' tree.

Ok. I'm asking just because I'm preparing a PR to drop the workaround code in openQA and I'm wondering when that could be merged. Other than that I don't see a reason to hurry here.

...

Thanks so much for testing!

Can I add a "Tested-by: Fabian Vogt <fvogt@suse.com>" tag to the patches that you tested?

Yep! The openQA tests aren't exhaustive, but definitely count as a representative smoke test.

Yes indeed. In fact looking into these crashes caused by the remount RO made find another bug I ran into several months ago (at the time I didn't realize it could be caused by the remount RO). I'll submit the patchset upstream on monday, wait a few days for feedback and then merge them to the stable branch of kernel-source. Again, thanks for testing these! -- You are receiving this mail because: You are on the CC list for the bug.