From: Johannes Berg <johannes@sipsolutions.net>
To: Mattia Dongili <malattia@linux.it>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] sony-laptop: no need to unblock rfkill on load
Date: Tue, 09 Jun 2009 11:30:34 +0200 [thread overview]
Message-ID: <1244539834.4672.6.camel@johannes.local> (raw)
In-Reply-To: <20090609092112.GE7682@kamineko.org>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Tue, 2009-06-09 at 18:21 +0900, Mattia Dongili wrote:
> > It just bothered me because I was effectively reverting a recent commit.
> > I figuired I should let you know. In case it didn't work, when it was
> > merged you'd know why I did it and who to blame. But there is always Git
> > history for that :-).
>
> Errm... now that I look at that patch more closely, the code you're
> modifying is not upstream either.
> Anyway thanks for the ping, I'll take a look at what's going on in the
> wireless-testing tree ;)
Sorry, I guess I forgot to copy you on the rfkill rewrite. Basically
I've rewritten the rfkill APIs and ported sony. Bug
http://bugzilla.kernel.org/show_bug.cgi?id=13458 is related to that too.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-06-09 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 10:31 [PATCH] sony-laptop: no need to unblock rfkill on load Alan Jenkins
2009-06-08 10:36 ` Johannes Berg
[not found] ` <1244457418.18863.8.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-08 22:49 ` Mattia Dongili
[not found] ` <20090608224915.GA4583-pM3i+3kAS8Rg9hUCZPvPmw@public.gmane.org>
2009-06-09 8:31 ` Alan Jenkins
2009-06-09 9:21 ` Mattia Dongili
2009-06-09 9:30 ` Johannes Berg [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=1244539834.4672.6.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=malattia@linux.it \
/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