From: Michael Buesch <mb@bu3sch.de>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-wireless@vger.kernel.org,
Bcm43xx-dev@lists.berlios.de
Subject: Re: [stable] [PATCH stable] b43: Reject new firmware early
Date: Thu, 7 Feb 2008 10:24:27 +0100 [thread overview]
Message-ID: <200802071024.27445.mb@bu3sch.de> (raw)
In-Reply-To: <20080207072624.GB15657@kroah.com>
On Thursday 07 February 2008 08:26:24 Greg KH wrote:
> On Sat, Jan 26, 2008 at 01:54:52PM +0100, Michael Buesch wrote:
> > We must reject new incompatible firmware early to avoid
> > running into strange transmission failures.
> >
> > The current development tree supports newer firmware revisions.
> > These revisions cause strange failures on the stable 2.6.24 kernel.
> > Add a check to avoid confusing users a lot.
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> Oh wait, I see why it's not in Linus's tree, it doesn't pertain :)
>
> I'll queue this up, sorry for the noise.
Yeah, Linus' tree does have support for this firmware revision we are
rejecting with this patch. :) This patch was lost in the 2.6.24
release cycle, so I'd like to push it through -stable to confuse users
less with strange warnings caused by using wrong firmware.
This patch doesn't remove any functionality or something, it simply
transforms a blowing up firmware into a nice error message. :)
--
Greetings Michael.
prev parent reply other threads:[~2008-02-07 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 12:54 [PATCH stable] b43: Reject new firmware early Michael Buesch
2008-02-07 7:25 ` [stable] " Greg KH
2008-02-07 7:26 ` Greg KH
2008-02-07 9:24 ` Michael Buesch [this message]
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=200802071024.27445.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@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).