From: "John W. Linville" <linville@tuxdriver.com>
To: Otto Solares <solca@guug.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Greg KH <greg@kroah.com>,
linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>,
Tim Gardner <tim.gardner@canonical.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH V2] b43legacy: Fix failure in rate-adjustment mechanism
Date: Wed, 10 Sep 2008 09:21:09 -0400 [thread overview]
Message-ID: <20080910132108.GA5216@tuxdriver.com> (raw)
In-Reply-To: <20080910064044.GB8669@guug.org>
On Wed, Sep 10, 2008 at 12:40:44AM -0600, Otto Solares wrote:
> On Mon, Sep 08, 2008 at 04:54:59PM -0400, John W. Linville wrote:
> > On Mon, Sep 08, 2008 at 11:22:43AM -0500, Larry Finger wrote:
> > > Greg KH wrote:
> > >>
> > >> Bug fixes, not new features, it's pretty simple :)
> > >
> > > Just bug fixes, or does it have to be a regression?
> >
> > As I understand it, the rule is more like "bug fixes that are committed
> > in the linux-2.6 tree". Since Linus has become more strict about
> > requiring "regressions only" after the merge window, that effectively
> > enforces the "regressions only" rule on the -stable trees as well.
>
> In this case that rule is harming, is not idiotic to not accept bug
> fixes early or later?
I'm just the messenger...FWIW the argument is that even a "fix"
can introduce a new "bug" somewhere else, often quite unexpectedly.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-09-10 13:21 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
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 [this message]
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=20080910132108.GA5216@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=solca@guug.org \
--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).