http://bugzilla.suse.com/show_bug.cgi?id=1049599 http://bugzilla.suse.com/show_bug.cgi?id=1049599#c12 --- Comment #12 from Coly Li <colyli@suse.com> --- (In reply to Takashi Iwai from comment #11)

(In reply to Coly Li from comment #10)

...

(In reply to Takashi Iwai from comment #9)

...

(In reply to Coly Li from comment #7)

...

Let me have a look on this, please give me some hint. Should I get kernel source from branch origin/openSUSE-42.3 ?

The bug was detected on 4.12, i.e. stable branch.

Hi Takashi,

Get it. There are two questions more from me, 1) The fix is not upstream yet, can I submit it to stable branch now?

Well, is there any reason you can't submit to upstream? If not, at least, please submit the patch. An in-house patch can be applied to our kernel, but we really should try to follow our own "upstream-first" rule.

Because I see the branch name is stable. A rule for stable tree is patch should go into mainline kernel firstly, then go into stable. This patch is in md development tree, I guess it will still take some time for it going into 4.12 stable tree. So is it Okey for me to submit this patch into stable branch of openSUSE kernel ?

From your answer, I feel you would mean: fix it now.

...

2) I guess it should be in stable branch of openSUSE tree on https://github.com/openSUSE/kernel-source/tree/stable, am I right ?

Yes.

The kernel git tree is shared by both SUSE and openSUSE, BTW. It's the very same kernel-source.git tree you're working on everyday.

Got it, thanks. Coly -- You are receiving this mail because: You are on the CC list for the bug.