public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Schmauss, Erik" <erik.schmauss@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	stable <stable@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH 05/11] ACPICA: AML Parser: skip opcodes that open a scope upon parse failure
Date: Mon, 13 Aug 2018 20:51:24 +0200	[thread overview]
Message-ID: <20180813185124.GA5606@kroah.com> (raw)
In-Reply-To: <CF6A88132359CE47947DB4C6E1709ED53BB67573@ORSMSX110.amr.corp.intel.com>

On Mon, Aug 13, 2018 at 05:52:49PM +0000, Schmauss, Erik wrote:
> 
> 
> > -----Original Message-----
> > From: Rafael J. Wysocki [mailto:rafael@kernel.org]
> > Sent: Sunday, August 12, 2018 2:47 AM
> > To: Schmauss, Erik <erik.schmauss@intel.com>
> > Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>; Rafael J. Wysocki
> > <rjw@rjwysocki.net>
> > Subject: Re: [PATCH 05/11] ACPICA: AML Parser: skip opcodes that open a scope
> > upon parse failure
> > 
> > On Fri, Aug 10, 2018 at 11:45 PM Erik Schmauss <erik.schmauss@intel.com>
> > wrote:
> > >
> > > This change skips the entire length of opcodes that open a scope
> > > (Device, Scope, Processor, etc) if the creation of the op fails. The
> > > failure could be caused by various errors including AE_ALREADY_EXISTS
> > > and AE_NOT_FOUND.
> > >
> > > Reported-by: Jeremy Linton <jeremy.linton@arm.com>
> > > Tested-by: Jeremy Linton <jeremy.linton@arm.com>
> > > Signed-off-by: Erik Schmauss <erik.schmauss@intel.com>
> > 
> > I think that we should propagate this fix to the "stable" kernel series, at least
> > 4.17.y and newer.  Do you agree?
> 
> Yes, I agree.
> 
> Hi Greg, please add this to the stable kernel

What commit id should I add to the stable kernel?

thanks,

greg k-h

  reply	other threads:[~2018-08-13 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180810214304.13475-1-erik.schmauss@intel.com>
     [not found] ` <20180810214304.13475-6-erik.schmauss@intel.com>
     [not found]   ` <CAJZ5v0j1TSF39Y5xt4T3OsTfOFjafUiXvQOAjedxV8sA0Mn6-w@mail.gmail.com>
2018-08-13 17:52     ` [PATCH 05/11] ACPICA: AML Parser: skip opcodes that open a scope upon parse failure Schmauss, Erik
2018-08-13 18:51       ` Greg KH [this message]
2018-08-13 21:35         ` Rafael J. Wysocki

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=20180813185124.GA5606@kroah.com \
    --to=greg@kroah.com \
    --cc=erik.schmauss@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox