From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomas.winkler@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] update rfkill.h from kernel 2.6.33
Date: Tue, 19 Jan 2010 10:02:15 -0800 [thread overview]
Message-ID: <43e72e891001191002q10ee8359wfffa813b3db8a0d2@mail.gmail.com> (raw)
In-Reply-To: <1263923968.28066.2.camel@johannes.local>
On Tue, Jan 19, 2010 at 9:59 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Tue, 2010-01-19 at 09:57 -0800, Luis R. Rodriguez wrote:
>> On Tue, Jan 19, 2010 at 9:55 AM, Johannes Berg
>> <johannes@sipsolutions.net> wrote:
>> > On Tue, 2010-01-19 at 09:53 -0800, Luis R. Rodriguez wrote:
>> >> On Mon, Jan 18, 2010 at 11:05 PM, Tomas Winkler
>> >> <tomas.winkler@intel.com> wrote:
>> >> > 1. add FM radio type
>> >> > 2. update rfkill_type docs
>> >> >
>> >> > Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
>> >>
>> >> Why is this being pushed for 2.6.33 at this point?
>> >
>> > ??? Have you read the patch?
>>
>> So this is updating linux-next to get 2.6.33 rfkill stuff? How did
>> that happen?
>
> You still haven't read it? :)
>
> It's for rfkill userspace.
Jeesh, sorry about that. Monday e-mail trigger happy.
Luis
next prev parent reply other threads:[~2010-01-19 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 7:05 [PATCH 1/1] update rfkill.h from kernel 2.6.33 Tomas Winkler
2010-01-19 17:53 ` Luis R. Rodriguez
2010-01-19 17:55 ` Johannes Berg
2010-01-19 17:57 ` Luis R. Rodriguez
2010-01-19 17:59 ` Johannes Berg
2010-01-19 18:02 ` Luis R. Rodriguez [this message]
2010-01-20 22:30 ` Tomas Winkler
2010-01-22 0:44 ` Henrique de Moraes Holschuh
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=43e72e891001191002q10ee8359wfffa813b3db8a0d2@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomas.winkler@intel.com \
/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