[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Vf6x4-AYPPEMf7qXTi-RF92mdUn6rhghBpJ5avQAjYRzA@mail.gmail.com>
Date: Fri, 26 Nov 2021 16:51:00 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Henning Schild <henning.schild@...mens.com>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
linux-watchdog@...r.kernel.org,
Srikanth Krishnakar <skrishnakar@...il.com>,
Jan Kiszka <jan.kiszka@...mens.com>,
Gerd Haeussler <gerd.haeussler.ext@...mens.com>,
Guenter Roeck <linux@...ck-us.net>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Mark Gross <mgross@...ux.intel.com>,
Hans de Goede <hdegoede@...hat.com>,
Pavel Machek <pavel@....cz>, Enrico Weigelt <lkml@...ux.net>,
Michael Haener <michael.haener@...mens.com>
Subject: Re: [PATCH v4 4/4] platform/x86: pmc_atom: improve critclk_systems
matching for Siemens PCs
On Fri, Nov 26, 2021 at 4:10 PM Henning Schild
<henning.schild@...mens.com> wrote:
>
> Siemens industrial PCs unfortunately can not always be properly
> identified the way we used to. An earlier commit introduced code that
> allows proper identification without looking at DMI strings that could
> differ based on product branding.
> Switch over to that proper way and revert commits that used to collect
> the machines based on unstable strings.
Usually we start a series with fixes, but I guess it's fine here since
this can be taken separately, right?
...
> +#include <linux/platform_data/x86/simatic-ipc.h>
Seems not. Question is then, what Fixes tags would mean in this case?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists