linux-kernel - Re: stable-3.1: iwlwifi broken with nomsi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111202234230.GA3671@kroah.com>
Date:	Fri, 2 Dec 2011 15:42:30 -0800
From:	Greg KH <greg@...ah.com>
To:	"Guy, Wey-Yi" <wey-yi.w.guy@...el.com>
Cc:	Johan Hovold <jhovold@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: stable-3.1: iwlwifi broken with nomsi

On Fri, Dec 02, 2011 at 02:39:44PM -0800, Guy, Wey-Yi wrote:
> Hi Greg,
> 
> On Fri, 2011-12-02 at 15:32 -0800, Greg KH wrote:
> > On Fri, Dec 02, 2011 at 02:28:42PM -0800, Guy, Wey-Yi wrote:
> > > On Fri, 2011-12-02 at 15:18 -0800, Greg KH wrote:
> > > > On Mon, Nov 28, 2011 at 08:59:39PM +0100, Johan Hovold wrote:
> > > > > Hi Greg, 
> > > > > 
> > > > > I believe commit 63665158282dd3b5d70 (iwlwifi: allow pci_enable_msi fail)
> > > > > needs to be added to the 3.1 stable tree as the driver fails to probe
> > > > > with MSI disabled since commit 084dd79172cb3 (iwlagn: move PCI related
> > > > > operations from probe and remove to PCI layer) without it:
> > > > 
> > > > I do not see commit 63665158282dd3b5d70 in Linus's tree, did you get it
> > > > incorrect?
> > > > 
> > > > confused,
> > > > 
> > > it is commit#8a39ef8ba0fa0410d71db8e981e887fe4fdeca88 in Linville's
> > > wireless tree
> > 
> > How nice, and what exactly can I do with that at this point in time?
> > 
> Can I send the patch to you for stable 3.1?

Again:

> > Come on, please go read Documentation/stable_kernel_rules.txt again for
> > how to do this properly...

Please read that and see _HOW_ to do this, and what the requirements are.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/