From: "John W. Linville" <linville@tuxdriver.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-04-07
Date: Wed, 9 Apr 2008 11:46:28 -0400 [thread overview]
Message-ID: <20080409154628.GB1298@tuxdriver.com> (raw)
In-Reply-To: <20080408030651.GA8849@tuxdriver.com>
On Mon, Apr 07, 2008 at 11:06:51PM -0400, John W. Linville wrote:
> Dave,
>
> Here is another batch of fixes intended for 2.6.25 if at all possible.
> We are mostly down to a smattering of one-liners, but there is a little
> fix that keeps b43legacy from crashing with certain bcm4303 hardware.
>
> Let me know if there are problems!
>
> Thanks,
>
> John
I'm revising this with three more patches. Please wait for the
next request.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-04-09 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 3:06 pull request: wireless-2.6 2008-04-07 John W. Linville
2008-04-09 15:46 ` John W. Linville [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=20080409154628.GB1298@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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).