From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Hans de Goede <hdegoede@redhat.com>
Cc: walter59 <walter.moeller@moeller-it.net>,
Adrien <kernel@asdrip.fr>, LKML <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [regression] Bug 216904 - backlight brighness control with video missing /sys/class/backlight interface
Date: Fri, 17 Feb 2023 13:16:39 +0100 [thread overview]
Message-ID: <8a998aba-7e71-da0d-6167-304dea3f2077@leemhuis.info> (raw)
In-Reply-To: <57e2f165-4d4a-d8bc-47c0-1b0609cd2147@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 12.01.23 15:14, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
>
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developer don't keep an eye on it, I decided to forward it by
> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=216904 :
#regzbot inconclusive: it appears that dropping acpi_backlight=vendor
solves this
#regzbot ignore-activity
(at least it did for somebody else that was affected by this; the
reporter did not respond in a while)
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.
prev parent reply other threads:[~2023-02-17 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 14:14 [regression] Bug 216904 - backlight brighness control with video missing /sys/class/backlight interface Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-17 12:16 ` 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=8a998aba-7e71-da0d-6167-304dea3f2077@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=hdegoede@redhat.com \
--cc=kernel@asdrip.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=walter.moeller@moeller-it.net \
/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).