From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Nori, Sekhar" <nsekhar@ti.com>
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: Tue, 19 Jul 2011 11:55:32 +0100 [thread overview]
Message-ID: <20110719105532.GF26574@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024DBDC68A@dbde02.ent.ti.com>
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.
next prev parent reply other threads:[~2011-07-19 10:55 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 [this message]
2011-07-20 16:40 ` Nori, Sekhar
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=20110719105532.GF26574@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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=nsekhar@ti.com \
/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®