From: Thorsten Leemhuis <email@example.com>
To: Benjamin Tissoires <firstname.lastname@example.org>,
Jiri Kosina <email@example.com>
Cc: firstname.lastname@example.org, LKML <email@example.com>,
"open list:HID CORE LAYER" <firstname.lastname@example.org>,
Subject: [Regression] Bug 216395 - XP-Pen Star G430S stops working on any kernel newer than 5.18.7
Date: Fri, 26 Aug 2022 13:00:57 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
Hi, this is your Linux kernel regression tracker.
I noticed a regression report in bugzilla.kernel.org that afaics nobody
acted upon since it was reported. That's why I decided to forward it by
mail to those that afaics should handle this.
To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216395 :
> firstname.lastname@example.org 2022-08-22 16:28:00 UTC
> XP-Pen Star G430S stops working on newer kernels than 5.18.7 (5.18.8, 5.19, 6.0rc1 tested)
> It seems to use the uclogic drivers.
See the ticket for details and further comments.
Please look into the issue if you're among the main recipients of this
mail (and not just CCed). I hope I picked the right people to sent this
to, if not just let everyone know (and apologies for getting it wrong!).
Anyway, to ensure this is not forgotten lets get this tracked by the the
Linux kernel regression tracking bot:
#regzbot introduced: v5.18..5.18.7
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report in bugzilla, as the kernel's documentation calls
for; above page explains why this is important for tracked regressions.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
next reply other threads:[~2022-08-26 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:00 Thorsten Leemhuis [this message]
2022-08-26 11:05 ` [Regression] Bug 216395 - XP-Pen Star G430S stops working on any kernel newer than 5.18.7 Jiri Kosina
2022-08-28 10:03 ` José Expósito
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).