From: Corentin Chary <corentin.chary@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] eeepc: fix kconfig problem
Date: Mon, 1 Jun 2009 22:07:58 +0200 [thread overview]
Message-ID: <71cd59b00906011307s54e8df13h475d4689e7025d4e@mail.gmail.com> (raw)
In-Reply-To: <4A23F6B5.6010000@oracle.com>
2009/6/1 Randy Dunlap <randy.dunlap@oracle.com>:
> Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20090529:
>
>
> Resend. linux-next still needs this patch.
>
> Len, what mailing list(s) should drivers/platform/x86/ patches
> be sent to?
>
Hi,
I believe the right list is linux-acpi.
Sorry, I forgot to join your patch to the last series I sent to Len.
Len, could you add this patch ?
Thanks
--
Corentin Chary
http://xf.iksaif.net - http://uffs.org
prev parent reply other threads:[~2009-06-01 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 10:05 linux-next: Tree for June 1 Stephen Rothwell
2009-06-01 15:41 ` [PATCH] eeepc: fix kconfig problem Randy Dunlap
2009-06-01 20:07 ` Corentin Chary [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=71cd59b00906011307s54e8df13h475d4689e7025d4e@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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