From: 'Greg KH' <greg@kroah.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: "Schmauss, Erik" <erik.schmauss@intel.com>,
stable@vger.kernel.org, 'Guenter Roeck' <linux@roeck-us.net>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Moore, Robert" <robert.moore@intel.com>
Subject: Re: Please revert "ACPICA: AML interpreter: add region addresses in global list during initialization"
Date: Wed, 28 Nov 2018 11:55:46 +0100 [thread overview]
Message-ID: <20181128105546.GA1822@kroah.com> (raw)
In-Reply-To: <20181128095627.38c8ca74@endymion>
On Wed, Nov 28, 2018 at 09:56:27AM +0100, Jean Delvare wrote:
> Hi Erik, Greg,
>
> On Wed, 28 Nov 2018 00:27:37 +0000, Schmauss, Erik wrote:
> > Here's an additional data point from the discussion on bz201721.
> > The user started using fancontrol during the period where resource conflict
> > checking was unintentionally removed. If the reporter tries using fancontrol
> > on 4.18.13, they report that fancontrol does not work. So it was basically
> > always the case that he needed to use acpi_resource_conflicts=lax for a short
> > period of time.
> >
> > I understand that this "breaks" this machine but we shouldn't be reverting
> > resource conflict checking for all other drivers just because of fancontrol. By
> > removing this check, we are suppressing warnings and changing the loading behavior
> > of other drivers as well.
>
> I agree. The incorrect (or at the very least incomplete and confusing)
> claims in bug #201721 made me think it was a regression from older
> versions. As it turns out that this isn't the case, my request to
> revert 4abb951b73ff0a8a979113ef185651aa3c8da19b from stable kernel
> series was incorrect. I apologize for the noise and ask Greg to undo
> the revert.
Ok, now added back, thanks.
greg k-h
prev parent reply other threads:[~2018-11-28 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:46 Please revert "ACPICA: AML interpreter: add region addresses in global list during initialization" Jean Delvare
2018-11-20 8:54 ` Greg KH
2018-11-20 9:03 ` Jean Delvare
2018-11-20 9:11 ` Greg KH
2018-11-20 18:30 ` Schmauss, Erik
2018-11-21 8:04 ` Greg KH
2018-11-22 1:30 ` Schmauss, Erik
2018-11-21 8:45 ` Jean Delvare
[not found] ` <CF6A88132359CE47947DB4C6E1709ED53C5508FA@ORSMSX122.amr.corp.intel.com>
2018-11-28 0:27 ` Schmauss, Erik
2018-11-28 8:56 ` Jean Delvare
2018-11-28 10:55 ` 'Greg KH' [this message]
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=20181128105546.GA1822@kroah.com \
--to=greg@kroah.com \
--cc=erik.schmauss@intel.com \
--cc=jdelvare@suse.de \
--cc=linux@roeck-us.net \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).