All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Will Keaney <keaneyw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v11] rfkill: rewrite
Date: Tue, 26 May 2009 15:15:38 +0200	[thread overview]
Message-ID: <20090526131533.GA3932@tuxdriver.com> (raw)
In-Reply-To: <4A1BDE51.7020009@gmail.com>

On Tue, May 26, 2009 at 08:19:29AM -0400, Will Keaney wrote:
> Johannes Berg wrote:
> > This patch completely rewrites the rfkill core to address
> > the following deficiencies:
> >   
> I applied this to a fresh pull of wireless-testing this morning, and
> haven't had any problems from it.  It looks like the soft lockup I
> reported earlier has been fixed.

Cool, thanks for the report.

I'm leaning towards merging this in time for the 2.6.31 merge
window...who wants to complain? :-)

John

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-05-26 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 21:52 [PATCH v10] rfkill: rewrite Johannes Berg
2009-05-23  8:44 ` [PATCH v11] " Johannes Berg
2009-05-26 12:19   ` Will Keaney
2009-05-26 13:15     ` John W. Linville [this message]
2009-05-26 13:32       ` Dan Williams
2009-05-26 13:48         ` Marcel Holtmann
2009-05-27  2:55       ` Henrique de Moraes Holschuh
2009-05-27  6:28         ` Johannes Berg
2009-05-27 14:00           ` Henrique de Moraes Holschuh
2009-05-27 14:24             ` Johannes Berg
2009-05-27 19:21               ` Henrique de Moraes Holschuh
2009-05-27  8:07         ` John W. Linville
2009-05-27 14:05           ` Henrique de Moraes Holschuh
2009-05-27 18:04           ` Dan Williams
2009-05-26 13:27     ` 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=20090526131533.GA3932@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=johannes@sipsolutions.net \
    --cc=keaneyw@gmail.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.