From: Greg KH <greg@kroah.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: Daniel Drake <dsd@gentoo.org>, Greg KH <gregkh@suse.de>,
torvalds@osdl.org, "Theodore Ts'o" <tytso@mit.edu>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Justin Forbes <jmforbes@linuxtx.org>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Dave Jones <davej@redhat.com>,
Chuck Wolber <chuckw@quantumlinux.com>,
stable@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] RE: [patch 10/26] ACPI: Prefer _CST over FADT for C-state capabilities
Date: Tue, 13 Dec 2005 13:48:28 -0800 [thread overview]
Message-ID: <20051213214828.GA16412@kroah.com> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300567E76B@hdsmsx401.amr.corp.intel.com>
On Tue, Dec 13, 2005 at 01:56:26PM -0500, Brown, Len wrote:
> yes, the 3rd patch should go with the first two.
> I asked Linus to pull the 3rd patch upstream
> http://lkml.org/lkml/2005/12/6/32
> but this was just as he cut -rc5 and headed out for a week.
>
> Linus,
> Can you pull that patch upstream before cutting 2.6.15?
>
> Thanks Daniel for the follow-up,
Can someone send the patch to stable@ when it goes in so I can include
it in the next round? I've moved the other two acpi patches for the
next release, pending this patch.
thanks,
greg k-h
next parent reply other threads:[~2005-12-13 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7DC2337C7631D4386A2DF6E8FB22B300567E76B@hdsmsx401.amr.corp.intel.com>
2005-12-13 21:48 ` Greg KH [this message]
2005-12-21 18:52 ` [patch 10/26] ACPI: Prefer _CST over FADT for C-state capabilities Daniel Drake
[not found] <20051213073430.558435000@press.kroah.org>
2005-12-13 8:22 ` Greg KH
2005-12-13 16:00 ` Daniel Drake
2005-12-13 18:11 ` [stable] " Greg KH
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=20051213214828.GA16412@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chuckw@quantumlinux.com \
--cc=davej@redhat.com \
--cc=dsd@gentoo.org \
--cc=gregkh@suse.de \
--cc=jmforbes@linuxtx.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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