From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Torsten Schenk <torsten.schenk@zoho.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: submitting patch: specify destination kernel version(s)
Date: Fri, 2 Sep 2011 14:57:03 +0100 [thread overview]
Message-ID: <20110902135702.GA10175@sirena.org.uk> (raw)
In-Reply-To: <1322a11922c.1088573675407063638.-3372964620296301533@zoho.com>
On Fri, Sep 02, 2011 at 02:16:27PM +0200, Torsten Schenk wrote:
Please fix your mailer to word wrap within paragraphs.
> I'm currently preparing a patch for the kernel, I want it to be included from 3.0 on, but not in versions before. I once got a hint to put
> Cc: stable@kernel.org
> but that seems not to do the trick. How could it be achieved, that the patch only appears in 3.0 (and later)?
What's the actual patch? Cc stable is the way to get patches picked up
for the stable kernel, if you want to limit the backports putting a note
in the changelog is probably sensible.
prev parent reply other threads:[~2011-09-02 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 12:16 submitting patch: specify destination kernel version(s) Torsten Schenk
2011-09-02 12:50 ` Daniel Mack
2011-09-02 13:57 ` Greg KH
2011-09-02 13:57 ` Mark Brown [this message]
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=20110902135702.GA10175@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=torsten.schenk@zoho.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.