From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Feng Tang <feng.tang@intel.com>
Cc: Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
paulmck@linux.vnet.ibm.com, Thomas Renninger <trenn@suse.de>,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ACPI processor: Fix a typo error in commit 99b725084
Date: Fri, 03 Aug 2012 11:43:50 +0530 [thread overview]
Message-ID: <501B6C1E.3060503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120803140343.0f15eebd@feng-i7>
On 08/03/2012 11:33 AM, Feng Tang wrote:
> On Fri, 3 Aug 2012 11:26:04 +0530
> "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com> wrote:
>
>> On 08/03/2012 09:52 AM, Len Brown wrote:
>>> Applied.
>>>
>>> thanks for the refresh.
>>>
>>
>> This patch needs to be CC'ed to stable also right?
>
> Yes, I've sent the patch directly to stable 3 days ago. thanks
> for the note.
>
Hmm? Patches are not accepted into the stable tree until the patch
goes upstream, IIUC. And to make a patch automatically go to -stable
once it hits mainline, you need to add Cc: stable@vger.kernel.org
among the Signed-off-by sequence in the patch.
Otherwise, we can explicitly mail the patch to stable, -after- the
corresponding patch hits mainline.. In fact, we will also have to quote
the mainline commit id in that.
See Documentation/stable_kernel_rules.txt for details.
Regards,
Srivatsa S. Bhat
prev parent reply other threads:[~2012-08-03 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 4:44 [PATCH v2] ACPI processor: Fix a typo error in commit 99b725084 Feng Tang
2012-07-31 9:26 ` Rafael J. Wysocki
2012-07-31 17:18 ` Deepthi Dharwar
2012-08-03 4:22 ` Len Brown
2012-08-03 5:56 ` Srivatsa S. Bhat
2012-08-03 6:03 ` Feng Tang
2012-08-03 6:13 ` Srivatsa S. Bhat [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=501B6C1E.3060503@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=deepthi@linux.vnet.ibm.com \
--cc=feng.tang@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=trenn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).