Message ID | 1463547892-11290-1-git-send-email-a@unstable.cc |
---|---|
State | Not Applicable, archived |
Headers | show |
On Wednesday 18 May 2016 13:04:44 Antonio Quartulli wrote: > I also have a question: I have another bugfix that should only be > applied to 4.6 and not to 4.7/net-next - should I directly send it > to stable@vger.kernel.org ? Allow me to give some background info: The bug was (accidentally) fixed by a refactoring patch [1] in net-next. But the problem was then discovered by people which used net and not net-next. I have created a bugfix [2] which would solve the problem in net but wouldn't apply in net-next. This is why Antonio asked if he should send it to stable@ or if there is a better way to get it integrated. Kind regards, Sven [1] https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/net/batman-adv?id=efcc9d3069c982786f380bca8480a1aa2fd2721d [2] https://git.open-mesh.org/linux-merge.git/commit/af06cf325cfb5a2685a6f8997585b83a91f36c4c
From: Antonio Quartulli <a@unstable.cc> Date: Wed, 18 May 2016 13:04:44 +0800 > these are the fixes that couldn't make it for linux-4.6 rebased on top > of net-next. > > They were all supposed to be applied on 4.6, therefore it would be nice > if you could queue them for inclusion in the 4.6.1 stable release. > > Please pull or let me know of any problem! Pulled, thanks. > I also have a question: I have another bugfix that should only be > applied to 4.6 and not to 4.7/net-next - should I directly send it > to stable@vger.kernel.org ? Yeah, why don't you send it directly to the stable list. Thanks.