From: Larry Finger <Larry.Finger@lwfinger.net>
To: David Ellingsworth <david@identd.dyndns.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFT/RFC 1/2] b43legacy: Fixes for beacons
Date: Thu, 26 Mar 2009 17:48:42 -0500 [thread overview]
Message-ID: <49CC064A.10304@lwfinger.net> (raw)
In-Reply-To: <30353c3d0903261426u56c47af9oe15d9775db171714@mail.gmail.com>
David Ellingsworth wrote:
>
> I haven't had a chance to test these as of yet. I had to wait a few
> extra days in order for my new wireless card to come in (couldn't
> really test in AP mode with only one card). I built a new kernel last
> night with these patches, but I still need to setup and configure
> hostapd. Hopefully, I'll know more later tonight. I'll run tests with
> and without these patches.
OK. Please take whatever time you need. We already missed to 2.6.30 merge
window, thus we have a couple of months.
Larry
next prev parent reply other threads:[~2009-03-26 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 19:58 [RFT/RFC 1/2] b43legacy: Fixes for beacons Larry Finger
2009-03-26 21:26 ` David Ellingsworth
2009-03-26 22:48 ` Larry Finger [this message]
2009-03-31 22:29 ` David Ellingsworth
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 4:17 Larry Finger
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=49CC064A.10304@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=david@identd.dyndns.org \
--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 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).