[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1AE640813FDE7649BE1B193DEA596E8802554D4E@SHSMSX101.ccr.corp.intel.com>
Date: Fri, 18 Apr 2014 06:36:48 +0000
From: "Zheng, Lv" <lv.zheng@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"Brown, Len" <len.brown@...el.com>, Lv Zheng <zetalog@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Zhao, Yakui" <yakui.zhao@...el.com>
Subject: RE: [PATCH] ACPICA: Tables: Skip NULL entries in RSDT and XSDT.
Hi,
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, April 18, 2014 11:40 AM
>
> On Fri, Apr 18, 2014 at 03:00:21AM +0000, Zheng, Lv wrote:
> > Hi, Greg
> >
> > > From: Greg KH [mailto:gregkh@...uxfoundation.org]
> > > Sent: Friday, April 18, 2014 10:44 AM
> > >
> > > On Fri, Apr 18, 2014 at 09:53:19AM +0800, Lv Zheng wrote:
> > > > Note that this patch is only used for stable kernels, upstream kernels
> > > > will have this problem fixed in ACPICA 201303-04 release. So upstream
> > > > kernels shouldn't merge this commit.
> > >
> > > What kernel commit fixed this issue in "upstream"?
> >
> > There is no kernel commit now has fixed this issue in "upstream".
> > The fix commit need to go into ACPICA first, so I believe it will
> > appear in 3.15-rc2 (ACPICA 201403xx release) or 3.15-rc3 (ACPICA
> > 201404xx release).
>
> Then I can't take this patch at all in any stable tree. Please read
> Documentation/stable_kernel_rules.txt for why and how to properly do
> this.
>
> Just mark the commit that fixes the issue in Linus's tree for stable,
> and it will happen automatically.
>
OK.
> > The back port of the fix commit will have many dependencies as we have
> > a big change in ACPICA table manager in ACPICA 201403xx release.
>
> Why not just submit this fix first to Linus, for his tree now, and then
> do the larger changes later?
>
OK. It seems possible now.
> > However this back port is very light and has been confirmed by the reporters.
> >
> > The bug seems to be urgent, it has broken many platforms shipped with
> > AMI BIOSes versioning from F2 to F4. Someone may monitor here to find
> > a valid fix.
>
> Not any stable maintainers, we can't take patches that aren't in Linus's
> tree, sorry.
>
OK.
I was just a little worried about as I'm the culprit.
Sorry for the noise.
Thanks and best regards
-Lv
> 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