Re: New USB ID 2001:3c25

[Willy Tarreau <w@1wt.eu>]

On Wed, Jun 03, 2015 at 09:01:09PM +0200, Bjørn Mork wrote:
> Willy Tarreau <w@1wt.eu> writes:
> > On Wed, Jun 03, 2015 at 05:50:49PM +0000, Scott Branden wrote:
> >> Hi Larry,
> >> 
> >> There is no problem applying this patch to the stable tree.
> >> I didn't know it was my responsibility to inform the stable mailing list every time a patch is accepted
> >> in the latest kernel that could be applied to the stable tree?
> >
> > Just adding a Cc: stable@... in the commit message is enough to get it
> > automatically queued once applied. Please check SubmittingPatches and
> > stable_kernel_rules.txt for more information.
> 
> It isn't absolutely clear to me that those rules applies to "wireless",
> being a sub-subsystem of "net".  Quoting from stable_kernel_rules.txt :
> 
> "- If the patch covers files in net/ or drivers/net please follow netdev stable
>    submission guidelines as described in
>    Documentation/networking/netdev-FAQ.txt"
> 
> And the netdev-FAQ.txt goes into great detail describing the procedure,
> which basically is "Give davem a hint that the patch should go to
> stable".  (and I'd like to note that this works very well in practice).
> 
> But I have noticed that some stable patches seem to flow more directly
> into stable from "wireless" than from the rest of "net". I just don't
> think the current _written_ docs support that procedure.  Those docs
> are possibly wrong?  You should probably know much better than me :)

I'd say that if it's something that you submit through the regular netdev
process, David will automatically handle the backports and feed stable if
he spots this is needed (hence sometimes some hints in the commit message
about what oldest version should benefit from the backport can help it get
properly spotted if there's any ambiguity). If you didn't go through that
process, there's almost no chance he will detect your work and propose it
and then it makes sense to Cc stable.

I know that sometimes it can be ambiguous, hence the benefit of being
the clearest possible in the commit message all the time so that anyone
could possibly detect that your work needs to be backported if it slips
through the process.

Regards,
Willy