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]
Date:	Wed, 16 Dec 2009 06:55:52 -0800
From:	Greg KH <greg@...ah.com>
To:	Ike Panhc <ike.pan@...onical.com>
Cc:	reinette chatre <reinette.chatre@...el.com>,
	"John W. Linville" <linville@...driver.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Winkler, Tomas" <tomas.winkler@...el.com>,
	"stable@...nel.org" <stable@...nel.org>,
	"Guy, Wey-Yi W" <wey-yi.w.guy@...el.com>,
	"Zhu, Yi" <yi.zhu@...el.com>
Subject: Re: [stable] [PATCH 2/2] iwlwifi: unify iwl_setup_rxon_timing

On Wed, Dec 16, 2009 at 02:46:10PM +0800, Ike Panhc wrote:
> Greg KH wrote:
> > On Tue, Dec 15, 2009 at 11:42:48AM -0800, reinette chatre wrote:
> >> On Tue, 2009-12-15 at 08:31 -0800, John W. Linville wrote:
> >>> On Tue, Dec 15, 2009 at 05:49:43AM -0800, Greg KH wrote:
> >>>> On Tue, Dec 15, 2009 at 03:02:17PM +0800, Ike Panhc wrote:
> >>>>> Please consider applying to linux-2.6.31.y
> >>>> I need the subsystem maintainer to agree with this, have they?
> >>> It seems fine to me.  You may want to let Intel comment too.
> >>>
> >> No objection here. Even so, I find it strange that this patch fixes a
> >> problem since it really should not have any functional changes. 
> > 
> > Ok, if there is no functional change, why is this needed?
> > 
> > Ike?
> > 
> > thanks,
> > 
> > greg k-h
> I review the patch again. Yes, it is no functional change. Sorry I have
> misunderstanding about the patch. Please do not put the second patch into
> stable.

Ok, will do.

> But Please consider applying the first patch (change IWL6000_UCODE_API_MAX
> to v4) to 2.6.31-stable tree. It will be good to use v4 firmware on iwl6000.

Why, what bug does it fix?  Will it require users to update their
firmware versions on their system as well?

thanks,

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ