From: "John W. Linville" <linville@tuxdriver.com>
To: Daniel Drake <dsd@gentoo.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH,RFT] bcm43xx: use softmac-suggested TX rate
Date: Fri, 19 May 2006 14:08:51 -0400 [thread overview]
Message-ID: <20060519180846.GE30177@tuxdriver.com> (raw)
In-Reply-To: <20060506091651.26BCD88A2C3@zog.reactivated.net>
On Sat, May 06, 2006 at 10:16:51AM +0100, Daniel Drake wrote:
> Can a bcm43xx user please test this. It uses the new txrate stuff found in
> the wireless-dev tree.
Daniel,
Do you intend for this to be merged? Given recent miscommunication,
I figured I should ask... :-)
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-05-19 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 9:16 [PATCH,RFT] bcm43xx: use softmac-suggested TX rate Daniel Drake
2006-05-19 18:08 ` John W. Linville [this message]
2006-05-19 18:44 ` Daniel Drake
2006-05-19 18:32 ` Michael Buesch
2006-06-05 18:51 ` John W. Linville
2006-06-05 19:15 ` Michael Buesch
2006-06-05 19:17 ` John W. Linville
2006-06-05 19:28 ` Michael Buesch
2006-06-05 19:42 ` John W. Linville
2006-06-05 19:48 ` Daniel Drake
2006-06-05 20:00 ` John W. Linville
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=20060519180846.GE30177@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dsd@gentoo.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).