From: Michael Buesch <mb@bu3sch.de>
To: bcm43xx-dev@lists.berlios.de
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH RFC/RFT] b43: Rewrite TX power adjustment
Date: Mon, 28 Jul 2008 20:17:04 +0200 [thread overview]
Message-ID: <200807282017.04979.mb@bu3sch.de> (raw)
In-Reply-To: <200807261726.53279.mb@bu3sch.de>
On Saturday 26 July 2008 17:26:52 Michael Buesch wrote:
> This is an experimental attempt for fixing the currently-not-so-good
> TX power adjustment.
Hm, is anybody going to test this, or are there really no transmission
problems left? :)
But please note that current wireless-testing tree seems to have some
unrelated TX issues in mac80211 (see the discussions about the qdisc
and skb->cb stuff.)
In any case, I'd like to have some initial testing of this patch? :)
I think it really is a good step forward, once all bugs in it are fixed.
--
Greetings Michael.
next prev parent reply other threads:[~2008-07-28 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 15:26 [PATCH RFC/RFT] b43: Rewrite TX power adjustment Michael Buesch
2008-07-28 18:17 ` Michael Buesch [this message]
2008-07-28 22:51 ` Larry Finger
2008-07-29 12:53 ` Michael Buesch
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=200807282017.04979.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--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).