From: Chris Ball <cjb@laptop.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: sdhci-esdhc: break out early if clock is 0
Date: Mon, 27 Aug 2012 19:29:31 -0400 [thread overview]
Message-ID: <87ehmrykv8.fsf@octavius.laptop.org> (raw)
In-Reply-To: <CAAQ0ZWSpxAn+F45C_tuW1Co1370-DVb=dXSzDt9GBy9Mq_vLqg@mail.gmail.com> (Shawn Guo's message of "Tue, 28 Aug 2012 07:14:50 +0800")
Hi,
On Mon, Aug 27 2012, Shawn Guo wrote:
> On 28 August 2012 07:07, Chris Ball <cjb@laptop.org> wrote:
>> Thanks, pushed to mmc-next for 3.6. (stable@ shouldn't be CC'd.)
>>
> I categorised it as a fix for a regression.
It is a fix for a regression, but the rules for submitting patches to
stable@ are significantly more strict than "is it a regression?".
>From Documentation/stable-kernel-rules.txt:
==
Rules on what kind of patches are accepted, and which ones are not, into the
"-stable" tree:
...
- It or an equivalent fix must already exist in Linus' tree (upstream).
Procedure for submitting patches to the -stable tree:
- Send the patch, after verifying that it follows the above rules, to
stable@vger.kernel.org. You must note the upstream commit ID in the
changelog of your submission, as well as the kernel version you wish
it to be applied to.
==
It doesn't already exist in mainline -- so it shouldn't have been
e-mailed to stable@ -- and even if it were already in mainline, you
shouldn't e-mail stable@ without including the upstream commit ID
and kernel version to apply it to. (Unless I'm missing something?)
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-08-27 23:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 15:10 [PATCH] mmc: sdhci-esdhc: break out early if clock is 0 Shawn Guo
2012-08-27 23:07 ` Chris Ball
2012-08-27 23:14 ` Shawn Guo
2012-08-27 23:29 ` Chris Ball [this message]
2012-08-28 0:00 ` Shawn Guo
2012-08-28 0:41 ` Chris Ball
2012-08-28 1:50 ` Shawn Guo
2012-08-28 3:43 ` Greg Kroah-Hartman
2012-08-28 11:04 ` Chris Ball
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=87ehmrykv8.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=linux-mmc@vger.kernel.org \
--cc=shawn.guo@linaro.org \
/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.