linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de,
	Larry Finger <Larry.Finger@lwfinger.net>,
	Tim Gardner <tim.gardner@canonical.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43legacy: Fix failure in rate-adjustment mechanism
Date: Sat, 6 Sep 2008 14:44:08 -0400	[thread overview]
Message-ID: <20080906184408.GA2923@tuxdriver.com> (raw)
In-Reply-To: <200809062041.06035.mb@bu3sch.de>

On Sat, Sep 06, 2008 at 08:41:05PM +0200, Michael Buesch wrote:
> On Saturday 06 September 2008 20:34:02 Larry Finger wrote:
> > A coding error present since b43legacy was incorporated into the
> > kernel has prevented the driver from using the rate-setting mechanism
> > of mac80211. The driver has been forced to remain at a 1 Mb/s rate.
> 
> Does version3 firmware have a different bitlayout for the status?
> 
> > Although this is not strictly a regression, it is a bug. I hope
> > it can be sent to 2.6.27.
> 
> The new rules don't allow us to fix bugs after the merge window.
> Only regressions.

I imagine the powers that be would claim it isn't a new rule, but it
is a new enforcement policy...

John

  reply	other threads:[~2008-09-07  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06 18:34 [PATCH] b43legacy: Fix failure in rate-adjustment mechanism Larry Finger
2008-09-06 18:41 ` Michael Buesch
2008-09-06 18:44   ` John W. Linville [this message]
2008-09-06 18:52   ` Larry Finger
2008-09-06 18:55     ` Michael Buesch
2008-09-06 18:57       ` Johannes Berg
2008-09-06 19:04         ` Michael Buesch
2008-09-06 19:36           ` Larry Finger
2008-09-06 19:41             ` Johannes Berg
2008-09-06 19:59               ` Larry Finger
2008-09-06 20:02                 ` Johannes Berg
2008-09-06 20:07                 ` 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=20080906184408.GA2923@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=tim.gardner@canonical.com \
    /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).