From: Mavroudis Chatzilazaridis <mavchatz@protonmail.com>
To: Jiri Kosina <jikos@kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "Bagas Sanjaya" <bagasdotme@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Input Devices" <linux-input@vger.kernel.org>,
"Filipe Laíns" <lains@riseup.net>,
"Bastien Nocera" <hadess@hadess.net>,
LinuxCat <masch77.linuxcat@gmail.com>,
Marcelo <mmbossoni@gmail.com>, "Takashi Iwai" <tiwai@suse.de>,
"Hans de Goede" <hdegoede@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Benjamin Tissoires" <benjamin.tissoires@redhat.com>
Subject: Re: Fwd: Logitech G915 Wireless Keyboard acts weird on 6.6.0
Date: Thu, 07 Dec 2023 15:04:19 +0000 [thread overview]
Message-ID: <1358c8e3-8495-461c-a8d8-a551cc4a0d11@protonmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2311211458030.29220@cbobk.fhfr.pm>
On 2023-11-21 16:00, Jiri Kosina wrote:> A comment from Mavroudis just
appeared in
>
> https://bugzilla.kernel.org/show_bug.cgi?id=218172
>
> pointing out that indeed the report descriptor of the device he is working
> on is different than the ones from the reporter.
>
> Until this mess gets figured out, I am now pretty sure revert is the way
> to go for 6.7.
>
> --
> Jiri Kosina
> SUSE Labs
>
Greetings everyone,
I have recently made a new patch [0] aimed at addressing the issues that
have been identified.
I would appreciate it if you could test it and provide any feedback on it.
[0] https://bugzilla.kernel.org/show_bug.cgi?id=218172#c14
prev parent reply other threads:[~2023-12-07 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 14:11 Fwd: Logitech G915 Wireless Keyboard acts weird on 6.6.0 Bagas Sanjaya
2023-11-21 13:09 ` Bagas Sanjaya
2023-11-21 13:37 ` Jiri Kosina
2023-11-21 13:58 ` Bagas Sanjaya
2023-11-21 14:15 ` Mavroudis Chatzilazaridis
2023-11-21 13:53 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-21 14:00 ` Bagas Sanjaya
2023-11-21 14:00 ` Jiri Kosina
2023-11-21 14:03 ` Bagas Sanjaya
2023-12-07 15:04 ` Mavroudis Chatzilazaridis [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=1358c8e3-8495-461c-a8d8-a551cc4a0d11@protonmail.com \
--to=mavchatz@protonmail.com \
--cc=bagasdotme@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=lains@riseup.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masch77.linuxcat@gmail.com \
--cc=mmbossoni@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.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).