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:	Thu, 31 Oct 2013 13:22:11 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Lv Zheng <lv.zheng@...el.com>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Bob Moore <robert.moore@...el.com>
Subject: Re: [PATCH 0/4] ACPICA: Stable material of ACPI executer fixes for linux-3.8.

On Thursday, October 31, 2013 05:08:50 AM Greg Kroah-Hartman wrote:
> On Thu, Oct 31, 2013 at 12:39:21PM +0100, Rafael J. Wysocki wrote:
> > On Thursday, October 31, 2013 09:07:40 AM Lv Zheng wrote:
> > > There are bug-fixes for AML interpreter upstreamed, fixing some serious
> > > issues found in recent platforms.  These fixes make Linux AML interpreter
> > > more ACPI 2.0 ASL concept compliant.  Further AML interpreter fixes should
> > > be based on such improvements, thus they are good materials for stable.
> > > 
> > > This patch set can be safely applied to linux-3.8:
> > > commit 19f949f52599ba7c3f67a5897ac6be14bfcb1200 upstream.
> > > 
> > > The patch set has passed build/boot tests on the following machines:
> > >   Dell Inspiron Mini 1010 (i386)
> > >   HP Compaq 8200 Elite SFF PC (x86-64)
> > > 
> > > Bob Moore (4):
> > >   ACPICA: Interpreter: Fix Store() when implicit conversion is not
> > >     possible.
> > >   ACPICA: DeRefOf operator: Update to fully resolve FieldUnit and
> > >     BufferField refs.
> > >   ACPICA: Return error if DerefOf resolves to a null package element.
> > >   ACPICA: Fix for a Store->ArgX when ArgX contains a reference to a
> > >     field.
> > 
> > Hi Greg,
> > 
> > Please take patches [1-4/4] for stable.
> 
> "Which" stable tree?
> 
> I don't do 3.8, it's long been end-of-life, although one company is
> trying to keep it alive, but that's not me.
> 
> I'm only handling 3.4, 3.10, and 3.11 stable trees right now, which
> one(s) should these be applied to?

3.10.x and 3.11.x then.

Lv, do the original mainline commits apply to these kernels?

Rafael

--
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