From: Chris Wright <chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Chris Wright <chrisw-69jw2NvuJkxg9hUCZPvPmw@public.gmane.org>,
Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Greek0-hi6Y0CQ0nG0@public.gmane.org
Subject: Re: [stable] Re: [patch 1/1] acpi: fix asus_acpi on Samsung P30/P35
Date: Wed, 4 Jan 2006 21:10:01 -0800 [thread overview]
Message-ID: <20060105051001.GG3335@sorel.sous-sol.org> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B300599D0BA-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
* Brown, Len (len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org) wrote:
> No reason except that I'm waiting for an -mm iteration
> before we pushing anything to 2.6.16. It has been 3 weeks
> since -mm shipped, so a lot has changed besides this
> and I'd like to see it all survive -mm before pushing to linus.
Sounds good, we can just wait for your cycle.
thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-05 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 3:27 [stable] Re: [patch 1/1] acpi: fix asus_acpi on Samsung P30/P35 Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B300599D0BA-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2006-01-05 5:10 ` Chris Wright [this message]
[not found] <F7DC2337C7631D4386A2DF6E8FB22B30059658DB@hdsmsx401.amr.corp.intel.com>
2006-01-04 16:37 ` Karol Kozimor
[not found] ` <20060104163729.GA6533-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2006-01-05 1:47 ` [stable] " Chris Wright
[not found] ` <20060105014707.GE3335-HBBaT/yk5SZXd/9EBkU14x2eb7JE58TQ@public.gmane.org>
2006-01-15 1:42 ` Karol Kozimor
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=20060105051001.GG3335@sorel.sous-sol.org \
--to=chrisw-69jw2nvujkxg9huczpvpmw@public.gmane.org \
--cc=Greek0-hi6Y0CQ0nG0@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.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