From: Greg KH <gregkh@linuxfoundation.org>
To: "Zheng, Lv" <lv.zheng@intel.com>
Cc: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Brown, Len" <len.brown@intel.com>, Lv Zheng <zetalog@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Zhao, Yakui" <yakui.zhao@intel.com>
Subject: Re: [PATCH] ACPICA: Tables: Skip NULL entries in RSDT and XSDT.
Date: Thu, 17 Apr 2014 20:39:45 -0700 [thread overview]
Message-ID: <20140418033945.GA20137@kroah.com> (raw)
In-Reply-To: <1AE640813FDE7649BE1B193DEA596E8802554BEC@SHSMSX101.ccr.corp.intel.com>
On Fri, Apr 18, 2014 at 03:00:21AM +0000, Zheng, Lv wrote:
> Hi, Greg
>
> > From: Greg KH [mailto:gregkh@linuxfoundation.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.
> 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?
> 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.
greg k-h
next prev parent reply other threads:[~2014-04-18 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 1:53 [PATCH] ACPICA: Tables: Skip NULL entries in RSDT and XSDT Lv Zheng
2014-04-18 1:53 ` Lv Zheng
2014-04-18 1:59 ` Zheng, Lv
2014-04-18 2:44 ` Greg KH
2014-04-18 3:00 ` Zheng, Lv
2014-04-18 3:39 ` Greg KH [this message]
2014-04-18 6:36 ` Zheng, Lv
2014-04-18 3:13 ` Zheng, Lv
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=20140418033945.GA20137@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=yakui.zhao@intel.com \
--cc=zetalog@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.