From: Michael Buesch <mb@bu3sch.de>
To: Greg KH <greg@kroah.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
John W Linville <linville@tuxdriver.com>,
Tim Gardner <tim.gardner@canonical.com>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH V2] b43legacy: Fix failure in rate-adjustment mechanism
Date: Mon, 8 Sep 2008 14:53:55 +0200 [thread overview]
Message-ID: <200809081453.56241.mb@bu3sch.de> (raw)
In-Reply-To: <20080908053155.GI4099@kroah.com>
On Monday 08 September 2008 07:31:55 Greg KH wrote:
> On Sun, Sep 07, 2008 at 12:40:04AM +0200, Michael Buesch wrote:
> > On Saturday 06 September 2008 23:51:22 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.
> > >
> > > Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> > > Cc: Stable <stable@kernel.org> [2.6.26], [2.6.25]
> >
> > Reviewed-by: Michael Buesch <mb@bu3sch.de>
> >
> > > ---
> > >
> > > John,
> > >
> > > This is a bug, not a regression. I guess under the new rules that it
> > > is 2.6.28 material.
> >
> > I wonder what the -stable rules are.
>
> Bug fixes, not new features, it's pretty simple :)
Yeah, well. My concern was:
- We put it into .25-stable and .26-stable, because it's a bugfix.
That's perfectly fine.
- We do _not_ put it into .27 mainline, because it is just a simple
bug, but not a regression. Instead we wait for .27-stable.
Doesn't make a lot sense to me. :)
So I'd like to see it in .27, too, despite the strict regressions-only
rule. A general regressions-only rule simply doesn't always make sense, IMO.
--
Greetings Michael.
next prev parent reply other threads:[~2008-09-08 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 21:51 [PATCH V2] b43legacy: Fix failure in rate-adjustment mechanism Larry Finger
2008-09-06 22:40 ` Michael Buesch
2008-09-08 5:31 ` Greg KH
2008-09-08 12:53 ` Michael Buesch [this message]
2008-09-08 16:22 ` Larry Finger
2008-09-08 20:54 ` John W. Linville
2008-09-10 6:40 ` Otto Solares
2008-09-10 13:21 ` John W. Linville
2008-09-10 5:19 ` Greg KH
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=200809081453.56241.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tim.gardner@canonical.com \
--cc=torvalds@linux-foundation.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).