From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: "Tomasz C." <tlinux@cebula.eu.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: FWD: Holtek mouse stopped working after kernel upgrade from 5.15.7 to 5.15.8
Date: Mon, 20 Dec 2021 15:09:45 +0100 [thread overview]
Message-ID: <CAO-hwJJxRETn3k0a_bXLMaD7rWNjWM8F9O0sv=jHtZuvJXa4aw@mail.gmail.com> (raw)
In-Reply-To: <4366861.LvFx2qVVIh@dell>
On Sat, Dec 18, 2021 at 9:39 PM Tomasz C. <tlinux@cebula.eu.org> wrote:
>
> Hello,
>
> I haven't had time to test it yet. But I see that another ArchLinux user has
> compiled kernel 5.15.10 with this patch and confirms that the mouse works.
> Details on:
> https://bugs.archlinux.org/task/73048#comment204441
>
> Is this enough for you as a test?
Yep, thanks a lot.
I have now pushed this to hid.git for-5.16/upstream-fixes with the
updated link, cc-ed stable and also added that archlinux bug.
Cheers,
Benjamin
>
> --
> Tomasz Cebula
> Dnia piątek, 17 grudnia 2021 09:37:11 CET Thorsten Leemhuis pisze:
>
> > Tomasz, could you give it a try please?
>
>
>
prev parent reply other threads:[~2021-12-20 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 7:00 FWD: Holtek mouse stopped working after kernel upgrade from 5.15.7 to 5.15.8 Thorsten Leemhuis
2021-12-17 7:17 ` Greg KH
2021-12-17 8:13 ` Benjamin Tissoires
2021-12-17 8:26 ` Greg KH
2021-12-17 8:29 ` Benjamin Tissoires
2021-12-17 8:37 ` Thorsten Leemhuis
2021-12-18 20:39 ` Tomasz C.
2021-12-20 14:09 ` Benjamin Tissoires [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='CAO-hwJJxRETn3k0a_bXLMaD7rWNjWM8F9O0sv=jHtZuvJXa4aw@mail.gmail.com' \
--to=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tlinux@cebula.eu.org \
/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).