From: "Krzysztof Olędzki" <ole@ans.pl>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
stable@vger.kernel.org
Subject: Re: Adding iTCO_wdt fixes into 4.9-stable?
Date: Mon, 19 Nov 2018 08:32:03 -0800 [thread overview]
Message-ID: <fc3feda7-ef16-9f64-b701-4ce2d6fd5499@ans.pl> (raw)
In-Reply-To: <20181119103125.GM4179@lahna.fi.intel.com>
+cc stable@vger.kernel.org
W dniu 2018-11-19 o 02:31, Mika Westerberg pisze:
> On Sun, Nov 18, 2018 at 07:13:18PM -0800, Krzysztof Olędzki wrote:
>> Hello Mika, Rafael, Greg,
>
> Hi,
>
>> Would it be possible to include the following two patches in 4.9-stable:
>> - "ACPI / watchdog: Prefer iTCO_wdt on Lenovo Z50-70"
>> - "ACPI / watchdog: Prefer iTCO_wdt always when WDAT table uses RTC SRAM"
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=a0a37862a4e1844793d39aca9ccb8fecbdcb8659
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=5a802a7a285c8877ca872e44eeb0f06afcb5212f
>>
>> Context: I just upgrade one of my servers from 4.4.161 to 4.9.137 and
>> run into a problem of not working RTC and watchdog. Adding these two
>> patches fixed the issue. No changes were necessary for them to be applied.
>
> I think the best way to get these included in stable trees is to send
> the commit ids with the above explanation to stable@vger.kernel.org.
Thank you Mika! I forgot how the process works. :/
The commits are:
a0a37862a4e1844793d39aca9ccb8fecbdcb8659
5a802a7a285c8877ca872e44eeb0f06afcb5212f
It also looks like the first patch is already in 4.14-stable, just not
in 4.9.
- a0a37862a4e1844793d39aca9ccb8fecbdcb8659 was included in 4.14.51:
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.51
However, it does not look like the 2nd one has been included in 4.14
yet. Would it be then possible to add
5a802a7a285c8877ca872e44eeb0f06afcb5212f to both 4.9-stable and 4.14-stable?
The impacted system is:
Dell Inc. PowerEdge T110 II/0PM2CW, BIOS 2.10.0 05/24/2018
Krzysztof
next parent reply other threads:[~2018-11-20 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <34c83ce4-b3ec-1cbf-db96-ad25ceabddd6@ans.pl>
[not found] ` <20181119103125.GM4179@lahna.fi.intel.com>
2018-11-19 16:32 ` Krzysztof Olędzki [this message]
2018-11-23 19:26 ` Adding iTCO_wdt fixes into 4.9-stable? Sasha Levin
2018-11-25 6:01 ` Krzysztof Olędzki
2018-11-26 9:24 ` Mika Westerberg
2018-11-26 10:00 ` Sasha Levin
2018-11-27 7:56 ` Krzysztof Olędzki
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=fc3feda7-ef16-9f64-b701-4ce2d6fd5499@ans.pl \
--to=ole@ans.pl \
--cc=gregkh@linuxfoundation.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@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