regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Bug 216930 - closing laptop lid wakes from suspend Lenovo Slim 7 Pro
Date: Tue, 21 Feb 2023 15:50:13 +0100	[thread overview]
Message-ID: <1a7d95b0-f148-a60c-21a9-3e331f07a53d@leemhuis.info> (raw)
In-Reply-To: <a4c166c1-d987-6966-8027-55ddd16e7d5d@leemhuis.info>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 30.01.23 10:36, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
> 
> I noticed a regression reported in bugzilla.kernel.org that seems to be
> handled there already, nevertheless I'd like to add to the tracking to
> ensure it's doesn't fall through the cracks in the end:
> 
> #regzbot introduced: v5.19..v6.0
> https://bugzilla.kernel.org/show_bug.cgi?id=216930
> #regzbot title: closing laptop lid wakes from suspend Lenovo Slim 7 Pro
> #regzbot ignore-activity

#regzbot inconclusive: unfixed, reporter doesn't care anymore (and
nobody ever bisected this)
#regzbot ignore-activity

https://bugzilla.kernel.org/show_bug.cgi?id=216930#c23

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

      reply	other threads:[~2023-02-21 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  9:36 Bug 216930 - closing laptop lid wakes from suspend Lenovo Slim 7 Pro Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-21 14:50 ` Linux regression tracking #update (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=1a7d95b0-f148-a60c-21a9-3e331f07a53d@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).