mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nori, Sekhar" <nsekhar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jon Povey <jon.povey@racelogic.co.uk>,
	"davinci-linux-open-source@linux.davincidsp.com" 
	<davinci-linux-open-source@linux.davincidsp.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"Hilman, Kevin" <khilman@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] davinci: fix DM365 EVM video input mux bits
Date: Wed, 20 Jul 2011 22:10:57 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024DC70E2A@dbde02.ent.ti.com> (raw)
In-Reply-To: <20110719105532.GF26574@n2100.arm.linux.org.uk>

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@kernel.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@kernel.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@kernel.org" to the commit text
but taking care to not actually send mail to stable@kernel.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@kernel.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

  reply	other threads:[~2011-07-20 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19  3:30 Jon Povey
2011-07-19  5:29 ` Hadli, Manjunath
2011-07-19  6:28   ` Jon Povey
2011-07-19  7:25     ` Hadli, Manjunath
2011-07-19  9:00       ` Nori, Sekhar
2011-07-19 10:24         ` Hadli, Manjunath
2011-07-19  8:56 ` Nori, Sekhar
2011-07-19 10:55   ` Russell King - ARM Linux
2011-07-20 16:40     ` Nori, Sekhar [this message]
2011-07-20 16:48       ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B85A65D85D7EB246BE421B3FB0FBB593024DC70E2A@dbde02.ent.ti.com \
    --to=nsekhar@ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=jon.povey@racelogic.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®