From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: netdev@vger.kernel.org
Subject: Re: rfkill rewrite bug
Date: Mon, 13 Apr 2009 20:56:54 +0200 [thread overview]
Message-ID: <1239649014.19457.1.camel@johannes.local> (raw)
In-Reply-To: <49E38BBC.5010708@tuffmail.co.uk> (sfid-20090413_205524_915082_56358705)
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Mon, 2009-04-13 at 20:00 +0100, Alan Jenkins wrote:
> Alan Jenkins wrote:
> > Johannes Berg wrote:
> >
> >> On Wed, 2009-04-08 at 14:37 +0100, Alan Jenkins wrote:
> >>
> >> You're right, and I'm rewriting rfkill and part of that is changing the
> >> maintainer to myself and the list to linux-wireless.
> >>
> >>
> >
> > Good luck! I'll try to have a look at your patch, to see how (if) it
> > would affect the benighted eeepc-laptop.
> >
>
> I tried the latest patch (#19) from your website, it didn't work so well
> :-).
:)
Thanks. I need to find some spare cycles to go through that patch again,
probably sometime this week.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-13 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:37 [PATCH] rfkill: document removal of notifier chain Alan Jenkins
2009-04-08 15:21 ` Johannes Berg
2009-04-08 17:21 ` Alan Jenkins
2009-04-13 19:00 ` rfkill rewrite bug Alan Jenkins
2009-04-13 18:56 ` Johannes Berg [this message]
2009-04-14 20:46 ` Johannes Berg
2009-04-18 8:17 ` Alan Jenkins
2009-04-18 8:15 ` Johannes Berg
2009-04-18 8:28 ` Johannes Berg
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=1239649014.19457.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).