From: Len Brown <lenb@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, stable@kernel.org,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [git pull request] ACPI patches for Linux 2.6.36-rc6
Date: Fri, 01 Oct 2010 19:31:57 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010011930220.6869@localhost.localdomain> (raw)
In-Reply-To: <201010012308.12897.rjw@sisk.pl>
> > commit 573b638158029898caf9470c8214b7ddd29751e3
> > Author: Colin Ian King <colin.king@canonical.com>
> > Date: Mon Aug 2 15:14:43 2010 +0000
>
> This one should go to -stable, shouldn't it?
yes, plus and a couple of the others.
FYI, I generally push to .stable when I go to delete the topic branches
that Linus has pulled and close applicable bug reports.
thanks,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-10-01 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 5:45 [git pull request] ACPI patches for Linux 2.6.36-rc6 Len Brown
2010-10-01 21:08 ` Rafael J. Wysocki
2010-10-01 23:31 ` Len 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=alpine.LFD.2.00.1010011930220.6869@localhost.localdomain \
--to=lenb@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox