linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] b43: RF-kill support
Date: Thu, 27 Sep 2007 18:08:08 -0500	[thread overview]
Message-ID: <46FC37D8.3000800@lwfinger.net> (raw)
In-Reply-To: <200709280033.35765.mb@bu3sch.de>

Michael Buesch wrote:
> One or two days, maybe.
> I'm currently debugging another important bug.
> And I guess I'll have to sleep in an hour or two, too. :)
> 
> The rfkill fix will be incremental based on this one, then.
> 

That I expected. The way I should have stated the question was "Should I submit the port of this
patch to b43legacy ASAP, or should I wait until the rfkill fix is ready to have only 1 rather than 2
patches for John to handle?" I think the correct answer is to wait. It will probably take me that
long to verify my port of the new LED handler anyway.

Larry


      reply	other threads:[~2007-09-27 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 19:35 [PATCH] b43: RF-kill support Michael Buesch
2007-09-27 20:54 ` Ivo van Doorn
2007-09-27 20:41   ` Michael Buesch
2007-09-27 21:12     ` Ivo van Doorn
2007-09-27 21:03       ` Michael Buesch
2007-09-27 21:23         ` Ivo van Doorn
2007-09-27 21:14           ` Michael Buesch
2007-09-27 21:43             ` Ivo van Doorn
2007-09-27 22:17         ` Larry Finger
2007-09-27 22:33           ` Michael Buesch
2007-09-27 23:08             ` Larry Finger [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=46FC37D8.3000800@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).