> -----Original Message----- > From: Greg Kroah-Hartman [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Thursday, November 29, 2018 7:01 AM > To: Jean Delvare <jdelvare@xxxxxxx> > Cc: linux-kernel@xxxxxxxxxxxxxxx; stable@xxxxxxxxxxxxxxx; Jean-Marc Lenoir > <archlinux@xxxxxxxxxxx>; Schmauss, Erik <erik.schmauss@xxxxxxxxx>; > Wysocki, Rafael J <rafael.j.wysocki@xxxxxxxxx> > Subject: Re: [PATCH 4.14 044/100] ACPICA: AML interpreter: add region > addresses in global list during initialization > > On Thu, Nov 29, 2018 at 03:45:26PM +0100, Jean Delvare wrote: > > Hi Greg, > > > > On Thu, 2018-11-29 at 15:12 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > know. > > > > > > ------------------ > > > > > > From: Erik Schmauss <erik.schmauss@xxxxxxxxx> > > > > > > commit 4abb951b73ff0a8a979113ef185651aa3c8da19b upstream. > > > > > > The table load process omitted adding the operation region address > > > range to the global list. This omission is problematic because the > > > OS queries the global list to check for address range conflicts > > > before deciding which drivers to load. This commit may result in > > > warning messages that look like the following: > > > > > > [ 7.871761] ACPI Warning: system_IO range 0x00000428-0x0000042F > conflicts with op_region 0x00000400-0x0000047F (\PMIO) > (20180531/utaddress-213) > > > [ 7.871769] ACPI: If an ACPI driver is available for this device, you should > use it instead of the native driver > > > > > > However, these messages do not signify regressions. It is a result > > > of properly adding address ranges within the global address list. > > > > > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=200011 > > > Tested-by: Jean-Marc Lenoir <archlinux@xxxxxxxxxxx> > > > Signed-off-by: Erik Schmauss <erik.schmauss@xxxxxxxxx> > > > Cc: All applicable <stable@xxxxxxxxxxxxxxx> > > > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > > Cc: Jean Delvare <jdelvare@xxxxxxx> > > > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > > > > I'm confused. While we were discussing the regression, Erik said that > > this is fixing commit 5a8361f7ecceaed64b4064000d16cb703462be49, which > > went upstream in v4.17. So how can the fix be needed in any kernel > > older than v4.17? Erik, did I understand you incorrectly? > Hi Greg, > The patch says "All applicable", and I assumed that meant, "as long as it > applies." > > Erik, should I drop this from 4.14.y? This should only apply to 4.17 or later. I unintentionally put all applicable so please drop this for all 4.16 or earlier. I've learned my lesson and I'll put the correct tags from now on :-) Erik > > thanks, > > greg k-h
