From: Jan Kiszka <jan.kiszka@siemens.com>
To: Michael Marley <michael@michaelmarley.com>,
Jean Delvare <jdelvare@suse.de>,
linux-watchdog@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: Faulty commit "watchdog: iTCO_wdt: Account for rebooting on second timeout"
Date: Wed, 4 Aug 2021 08:58:16 +0200 [thread overview]
Message-ID: <788533fa-0b77-4c44-2906-d8c9b2b8997d@siemens.com> (raw)
In-Reply-To: <934e0af4-3c4c-3ac5-30e2-958f0725a21d@michaelmarley.com>
On 04.08.21 02:04, Michael Marley wrote:
> On 8/3/21 10:59 AM, Jan Kiszka wrote:
>
>> https://lkml.org/lkml/2021/7/26/349
>>
>
> It fixes the problem for me (the person who opened the Bugzilla report)
> too, thanks!
>
> Tested-by: Michael Marley <michael@michaelmarley.com>
>
Thanks for the confirmation!
Yeah, sorry, that original mistake is truly mine. In fact, I wrote this
code twice [1] but only messed it up here. Unfortunate that it spread so
quickly. I'll try discuss this with stable people eventually, if it was
a one off or if there are more such cases.
Jan
[1]
https://github.com/siemens/efibootguard/commit/aa89fe3cbd883198c23eaec43c4448fe9e8ae148
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-08-04 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 14:51 Faulty commit "watchdog: iTCO_wdt: Account for rebooting on second timeout" Jean Delvare
2021-08-03 14:59 ` Jan Kiszka
2021-08-03 15:01 ` Jan Kiszka
2021-08-03 15:27 ` Guenter Roeck
2021-08-03 15:32 ` Jean Delvare
2021-08-04 0:04 ` Michael Marley
2021-08-04 6:58 ` Jan Kiszka [this message]
2021-08-06 6:28 ` Greg KH
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=788533fa-0b77-4c44-2906-d8c9b2b8997d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michael@michaelmarley.com \
--cc=stable@vger.kernel.org \
--cc=wim@linux-watchdog.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).