stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v1] platform/x86: pmc_atom: Add Siemens SIMATIC IPC227E to critclk_systems DMI table
Date: Fri, 8 Nov 2019 14:24:23 +0100	[thread overview]
Message-ID: <e448f04b-ea0c-f0b7-a8fe-f4952144dc09@siemens.com> (raw)
In-Reply-To: <20191108131813.GD761587@kroah.com>

On 08.11.19 14:18, Greg Kroah-Hartman wrote:
> On Thu, Nov 07, 2019 at 07:05:30PM +0200, Andy Shevchenko wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> The SIMATIC IPC227E uses the PMC clock for on-board components and gets
>> stuck during boot if the clock is disabled. Therefore, add this device
>> to the critical systems list.
>>
>> Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL")
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> ---
>>
>> - resend for stable inclusion
> 
> What git id is this in Linus's tree, and what tree(s) is this backport
> for?

Upstream ID ad0d315b4d4e7138f43acf03308192ec00e9614d.

We should target down to 4.14, the last stable kernel that got bothered 
by 648e921888ad as far as I can see.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2019-11-08 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07 17:05 [PATCH v1] platform/x86: pmc_atom: Add Siemens SIMATIC IPC227E to critclk_systems DMI table Andy Shevchenko
2019-11-07 23:59 ` Nobuhiro Iwamatsu
2019-11-08 13:18 ` Greg Kroah-Hartman
2019-11-08 13:24   ` Jan Kiszka [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=e448f04b-ea0c-f0b7-a8fe-f4952144dc09@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --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).