[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YnABLhyUGR+ZRQ+u@smile.fi.intel.com>
Date: Mon, 2 May 2022 19:05:02 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Paul Gortmaker <paul.gortmaker@...driver.com>,
linux-kernel@...r.kernel.org,
Aubrey Li <aubrey.li@...ux.intel.com>,
Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
Mark Gross <markgross@...nel.org>,
platform-driver-x86@...r.kernel.org,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH 0/4] platform: allow ATOM PMC code to be optional
On Mon, May 02, 2022 at 04:30:57PM +0200, Hans de Goede wrote:
> On 4/28/22 20:11, Paul Gortmaker wrote:
...
> As for users breaking support for BYT/CHT setups because they forget
> to enable this, without X86_INTEL_LPSS being enabled BYT/CHT are pretty
> much broken anyways and since patch 2/4 adds a "select PMC_ATOM" to the
> X86_INTEL_LPSS Kconfig option I'm not really worried about that.
>
> I'm afraid this patch-set might break some randomconfig builds though,
> but I cannot see anything obviously causing such breakage here, so
> I think it would be fine to just merge this series as is and then
> see if we get any breakage reports.
>
> Andy, are you ok with me moving ahead and merging this series as is?
It seems as is can't be fulfilled due to your own comment, but in general I'm
not objecting the idea. So, go ahead if you feel it's ready.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists