From: Matthew Garrett <mjg@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "John W. Linville" <linville@tuxdriver•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Johannes Berg <johannes@sipsolutions•net>,
Len Brown <lenb@kernel•org>
Subject: Re: linux-next: manual merge of the wireless tree with the acpi tree
Date: Wed, 3 Jun 2009 04:05:41 +0100 [thread overview]
Message-ID: <20090603030541.GC28009@srcf.ucam.org> (raw)
In-Reply-To: <20090603122724.ddf679ba.sfr@canb.auug.org.au>
Easiest in this case might be to drop the toshiba-acpi patches from me
from acpi-test for the moment - I'm still waiting for some testing
feedback on them. I can rebase against the rfkill code as long as it
lands early enough.
--
Matthew Garrett | mjg59@srcf•ucam.org
next prev parent reply other threads:[~2009-06-03 3:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 2:27 linux-next: manual merge of the wireless tree with the acpi tree Stephen Rothwell
2009-06-03 3:05 ` Matthew Garrett [this message]
2009-06-03 4:42 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-06-18 1:29 Stephen Rothwell
2009-06-03 2:20 Stephen Rothwell
2009-06-03 3:03 ` Matthew Garrett
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=20090603030541.GC28009@srcf.ucam.org \
--to=mjg@redhat$(echo .)com \
--cc=johannes@sipsolutions$(echo .)net \
--cc=lenb@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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