linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Linux regression tracking (Thorsten Leemhuis)" 
	<regressions@leemhuis.info>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux Input Devices <linux-input@vger.kernel.org>
Cc: "Mavroudis Chatzilazaridis" <mavchatz@protonmail.com>,
	"Filipe Laíns" <lains@riseup.net>,
	"Bastien Nocera" <hadess@hadess.net>,
	"Jiri Kosina" <jkosina@suse.cz>,
	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: Tue, 21 Nov 2023 21:00:43 +0700	[thread overview]
Message-ID: <ZVy4C9z99DbwEBBu@archie.me> (raw)
In-Reply-To: <0e10112a-7560-4dd8-8a03-5fdfc838168f@leemhuis.info>

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

On Tue, Nov 21, 2023 at 02:53:17PM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 21.11.23 14:09, Bagas Sanjaya wrote:
> > On Thu, Nov 02, 2023 at 09:11:42PM +0700, Bagas Sanjaya wrote:
> > <snip>...
> > There's no reply from culprit author nor linux-input people (did they
> > miss this regression?).
> 
> I guess part of the problem is that Bastien got reassigned and might not
> care about the kernel anymore.
> 
> Another part of it is that Jiri was CCed, but Benjamin was not.
> 
> Ideally of course Mavroudis Chatzilazaridis, the culprit's author would
> look into this, but from a quick search on lore it looks like Mavroudis
> is not a regular kernel contributor and thus might not even know how we
> expect situations like this to be handled.
> 
> > And on Bugzilla, other reporters replied that
> > reverting the culprit fixed the regression.
> 
> From Takashi's comments like
> https://bugzilla.kernel.org/show_bug.cgi?id=218094#c33 it sounds like
> this can be fixed by resolving another regression as discussed earlier
> today here:
> https://lore.kernel.org/all/87edgjo2kr.wl-tiwai@suse.de/
> 
> I think that might be the better solution, but Takashi, Hans, or the
> input people will know best.
> 
> > FYI, there's similar Bugzilla report on [1].
> > [1] https://bugzilla.kernel.org/show_bug.cgi?id=218172
> 
> Not sure, that might be a different problem, guess Hans is the best to
> judge.
> 
> > Also Cc'ed Linus.
> 
> Linus can speak for himself, but I guess he gets enough mail already.
> I'd say in a situation like this it thus might best to not CC him;
> instead poke me when things apparently are not handled well, then we
> together can decide if it's worth bringing Linus in.

Thanks for the pro tip!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-21 14:00 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 [this message]
2023-11-21 14:00     ` Jiri Kosina
2023-11-21 14:03       ` Bagas Sanjaya
2023-12-07 15:04       ` Mavroudis Chatzilazaridis

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=ZVy4C9z99DbwEBBu@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masch77.linuxcat@gmail.com \
    --cc=mavchatz@protonmail.com \
    --cc=mmbossoni@gmail.com \
    --cc=regressions@leemhuis.info \
    --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).