From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: tboot suspend broken on Lenovo T460p #forregzbot
Date: Thu, 8 Dec 2022 08:06:54 +0100 [thread overview]
Message-ID: <bf87ea86-9545-0f43-f444-16d2eaecda5d@leemhuis.info> (raw)
In-Reply-To: <ce38e824-2083-fcce-dc6c-2e6d58c132c2@leemhuis.info>
On 26.09.22 15:37, Thorsten Leemhuis wrote:
> TWIMC: this mail is primarily send for documentation purposes and for
> regzbot, my Linux kernel regression tracking bot. These mails usually
> contain '#forregzbot' in the subject, to make them easy to spot and filter.
>
> On 29.04.22 14:03, Thorsten Leemhuis wrote:
>> Hi, this is your Linux kernel regression tracker speaking.
>>
>> About a week ago a regression was reported to bugzilla.kernel.org that
>> seems to be handled there already, nevertheless I'd like to add to the
>> tracking to ensure it's not forgotten.
>>
>> #regzbot introduced: 453e41085183980087f8a80dada523caf1131c3c
>> #regzbot from: Derek Dolney <z23@posteo.net>
>> #regzbot title: tboot suspend broken on Lenovo T460p
>> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215867
>
>
> #regzbot backburner: fix available, but maintainer didn't pick it up and
> developer of the fix is MIA for unkown reason
#regzbot unbackburn
#regzbot fixed-by: 6f855b39e4602b6b
prev parent reply other threads:[~2022-12-08 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 12:03 tboot suspend broken on Lenovo T460p Thorsten Leemhuis
2022-09-26 13:37 ` tboot suspend broken on Lenovo T460p #forregzbot Thorsten Leemhuis
2022-12-08 7:06 ` Thorsten Leemhuis [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=bf87ea86-9545-0f43-f444-16d2eaecda5d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).