On Tue, 5 Oct 2010, Antonio Ospite wrote: > > > 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. Either you have to send it twice, or you can ad 'Cc: stable@xxxxxxxxxx' to the patch meta-information, and it will be picked up for stable automatically once it lands in Linus' tree. I have added the 'Cc:' markings now and applied both patches, thanks. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
