linux-kernel - RE: [PATCH] davinci: fix DM365 EVM video input mux bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Jul 2011 22:10:57 +0530
From:	"Nori, Sekhar" <nsekhar@...com>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Jon Povey <jon.povey@...elogic.co.uk>,
	"davinci-linux-open-source@...ux.davincidsp.com" 
	<davinci-linux-open-source@...ux.davincidsp.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"Hilman, Kevin" <khilman@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] davinci: fix DM365 EVM video input mux bits

Hi Russell,

On Tue, Jul 19, 2011 at 16:25:32, Russell King - ARM Linux wrote:
> On Tue, Jul 19, 2011 at 02:26:50PM +0530, Nori, Sekhar wrote:
> > Since this part of the code hasn't changed since it
> > was written, this is a good candidate for stable
> > kernel series. You can just add:
> > 
> > Cc: stable@...nel.org
> 
> Be careful when doing that - if you have git mail the patches out for
> review, and it picks that up, it'll send it to the stable team as well.
> The stable team will then complain "that's not how to submit patches
> to them".
> 
> So, while you can add "Cc: stable@...nel.org" to the patch, its best
> to only add that just before you publish the commit after review, but
> before merging.

But its very tough to guess what the last version
ready for merging will be. Review comments can come
at any stage.

Would adding "Cc: stable@...nel.org" to the commit text
but taking care to not actually send mail to stable@...nel.org
help? The stable_kernel_rules.txt document seems to suggest
this is an acceptable way:

"
- To have the patch automatically included in the stable tree, add the tag
     Cc: stable@...nel.org
   in the sign-off area. Once the patch is merged it will be applied to
   the stable tree without anything else needing to be done by the author
   or subsystem maintainer.
"

Thanks,
Sekhar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/