From: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
To: Greg KH <greg@kroah.com>
Cc: stable@linux.kernel.org, donald.h.fry@intel.com,
reinette.chatre@intel.com, wey-yi.w.guy@intel.com,
ilw@linux.intel.com, linville@tuxdriver.com, sgruszka@redhat.com,
ak@linux.intel.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] Please revert "iwlagn: Support new 5000 microcode." from 2.6.32 and 2.6.33
Date: Tue, 14 Jun 2011 22:14:44 -0300 [thread overview]
Message-ID: <20110615011443.GA13680@herton-IdeaPad-Y430> (raw)
In-Reply-To: <20110614230344.GA2065@kroah.com>
On Tue, Jun 14, 2011 at 04:03:44PM -0700, Greg KH wrote:
> On Mon, Jun 13, 2011 at 03:13:18PM -0300, Herton Ronaldo Krzesinski wrote:
> > The patch ("iwlagn: Support new 5000 microcode") shoudn't have been
> > applied on 2.6.32 and 2.6.33 stable trees, it doesn't support new
> > firmware file format, thus if the new firmware is on the disk, loading
> > fails, as reported on:
> > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/796336
> >
> > Support for the iwlagn new firmware file format was only added beginning
> > with 2.6.35 (commit "iwlagn: implement loading a new firmware file
> > type"), so iwlagn works with new firmware only with 2.6.35 or later.
>
> Can I get an ack from the developer of the patch and the people involved
> with it first? It was asked to be backported for a reason, so I would
> at least like to get the people who asked for the backport to have a
> chance to respond please.
>
> It's only nice, why would you exclude them?
I didn't intend to exclude anyone and I'm just reporting it, it didn't
came to my mind CC'ing people while sending to stable, and hopefully
everyone related are CC'ed now.
Also note that this revert request is for 2.6.32 and 2.6.33 *only*
And seems the right thing to do for them.
The other stable release where this was applied (2.6.35) looks fine
but these two are too old to support the new firmware (don't work, need
extra patches backported which weren't, like the commit I mentioned --
commit "iwlagn: implement loading a new firmware file type"), as yourself
can check reading the code/bug report, and what I wrote.
>
> greg k-h
>
--
[]'s
Herton
next parent reply other threads:[~2011-06-15 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110613181317.GA3385@herton-IdeaPad-Y430>
[not found] ` <20110614230344.GA2065@kroah.com>
2011-06-15 1:14 ` Herton Ronaldo Krzesinski [this message]
2011-06-15 5:57 ` [stable] Please revert "iwlagn: Support new 5000 microcode." from 2.6.32 and 2.6.33 Stanislaw Gruszka
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=20110615011443.GA13680@herton-IdeaPad-Y430 \
--to=herton.krzesinski@canonical.com \
--cc=ak@linux.intel.com \
--cc=donald.h.fry@intel.com \
--cc=greg@kroah.com \
--cc=ilw@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=sgruszka@redhat.com \
--cc=stable@linux.kernel.org \
--cc=wey-yi.w.guy@intel.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