linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "José Expósito" <jose.exposito89@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	gomapo2868@safe-cart.com, LKML <linux-kernel@vger.kernel.org>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Roman Romanenko <romu4444@gmail.com>,
	Nikolai Kondrashov <spbnick@gmail.com>
Subject: Re: [Regression] Bug 216395 - XP-Pen Star G430S stops working on any kernel newer than 5.18.7
Date: Sun, 28 Aug 2022 12:03:18 +0200	[thread overview]
Message-ID: <20220828100318.GB4121@elementary> (raw)
In-Reply-To: <nycvar.YFH.7.76.2208261304470.19850@cbobk.fhfr.pm>

Hi,

On Fri, Aug 26, 2022 at 01:05:44PM +0200, Jiri Kosina wrote:
> On Fri, 26 Aug 2022, Thorsten Leemhuis wrote:
> 
> > 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 :
> > 
> > >  gomapo2868@safe-cart.com 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.
> 
> Thorsten, thanks for the report.
> 
> CCing people who have been working on XP-Pen support recently (Roman, 
> Nikolai, José).
> 
> Keeping the rest of the mail below for reference.
> 
> > 
> > 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
> > https://bugzilla.kernel.org/show_bug.cgi?id=216395
> > #regzbot ignore-activity
> > 
> > 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:
> > https://linux-regtracking.leemhuis.info/tracked-regression/
> > 
> > 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.
> > 
> 
> -- 
> Jiri Kosina
> SUSE Labs
> 

I think that this bug report is similar to [1] and [2].

The issue was already solved by Benjamin with this patch [3].
If you can, please test his patch.

Best wishes,
Jose

[1] https://lore.kernel.org/linux-input/CAO-hwJ+MtU5w9M5rqbOPYjUUZtJ609Q0GwPJpy-9egDEjo9m7g@mail.gmail.com/T/
[2] https://bugzilla.kernel.org/show_bug.cgi?id=216106
[3] https://lore.kernel.org/linux-input/20220828095624.GA4121@elementary/T/

      reply	other threads:[~2022-08-28 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 11:00 [Regression] Bug 216395 - XP-Pen Star G430S stops working on any kernel newer than 5.18.7 Thorsten Leemhuis
2022-08-26 11:05 ` Jiri Kosina
2022-08-28 10:03   ` José Expósito [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=20220828100318.GB4121@elementary \
    --to=jose.exposito89@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=gomapo2868@safe-cart.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=romu4444@gmail.com \
    --cc=spbnick@gmail.com \
    /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).