On Tue, 5 Oct 2010 10:42:00 -0700 Greg KH <greg@xxxxxxxxx> wrote: > On Tue, Oct 05, 2010 at 05:20:15PM +0200, Antonio Ospite wrote: > > Hi, > > > > here are some fixes to hidraw. > > > > Patches are against 2.6.36-rc6, but they should be ported to other > > maintained stable kernels as well. > > [...] > > > > The first one has been sent already but I am resending it with > > stable@stable@kernel.org in the recipients list. > > Please read Documentation/stable_kernel_rules.txt which shows you how to > properly notify the stable developer to pick up the patch (hint, cc:ing > them on the patch is not the correct way, you need to add the mark to > the signed-off-by: area.) > I see now, thanks Greg. Jiri, are you adding the Cc: mark to these when you apply them? I misunderstood your previous statement about that and thought CCing like in recipients was enough. There is one thing which is not 100% clear to me from the doc (my fault): are patches targeted to -stable to be sent _twice_? Once for linus master branch (this is what "upstream" means in that context, isn't it?) and once for -stable with the commit ID of the former? Is the Cc mark meant just to automate this very process? It seemed to me that items 1 and 2 of the "Procedure" in Documentation/stable_kernel_rules.txt are alternative each other. Thanks, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Attachment:
pgpxsozlEHRzn.pgp
Description: PGP signature
