linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Filipe Laíns" <lains@riseup.net>,
	linux-input@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Thorsten Leemhuis" <regressions@leemhuis.info>
Subject: Re: [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[]
Date: Wed, 07 Dec 2022 13:43:23 +0100	[thread overview]
Message-ID: <f0ccee0d2f85099c146ee682b25d30c832155fa3.camel@hadess.net> (raw)
In-Reply-To: <nycvar.YFH.7.76.2212071117420.6045@cbobk.fhfr.pm>

On Wed, 2022-12-07 at 11:19 +0100, Jiri Kosina wrote:
> On Wed, 7 Dec 2022, Benjamin Tissoires wrote:
> 
> > Agree, but OTOH, Rafael, your mouse is not brand new AFAICT, so I
> > am 
> > worried that you won't be the only one complaining we just killed
> > their 
> > mouse. So I think the even wiser solution would be to delay (and so
> > revert in 6.1 or 6.2) the 2 patches that enable hid++ on all
> > logitech 
> > mice (8544c812e43ab7bdf40458411b83987b8cba924d and 
> > 532223c8ac57605a10e46dc0ab23dcf01c9acb43).
> 
> If we were not at -rc8 timeframe, I'd be in favor to coming up with
> proper 
> fix still for 6.1. But as things currently are, let's just revert
> those 
> and reschedule them with proper fix for 6.2+.

Has anyone seen any other reports?

Because, honestly, seeing work that adds support for dozens of devices
getting tossed out at the last minute based on a single report with no
opportunity to fix the problem is really frustrating.

  reply	other threads:[~2022-12-07 12:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 14:58 [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) Rafael J. Wysocki
2022-12-07  8:58 ` Rafael J. Wysocki
2022-12-07  9:07   ` Bastien Nocera
2022-12-07  9:04 ` Bastien Nocera
2022-12-07  9:16   ` Rafael J. Wysocki
2022-12-07  9:36     ` Rafael J. Wysocki
2022-12-07  9:58       ` Bastien Nocera
2022-12-07 10:07         ` Rafael J. Wysocki
2022-12-07 10:50           ` Bastien Nocera
2022-12-07 11:07             ` Rafael J. Wysocki
2022-12-07 17:19               ` Bastien Nocera
2022-12-07 17:44                 ` Rafael J. Wysocki
2022-12-08 15:20                   ` Bastien Nocera
2022-12-13 16:14                     ` Bastien Nocera
2022-12-15 15:09                       ` Rafael J. Wysocki
2022-12-07  9:10 ` [PATCH v1 0/2] HID: Fix regression resulting from commit 532223c8ac57 Rafael J. Wysocki
2022-12-07  9:11   ` [PATCH v1 1/2] HID: generic: Add ->match() check to __check_hid_generic() Rafael J. Wysocki
2022-12-07  9:27     ` Benjamin Tissoires
2022-12-07  9:54       ` Rafael J. Wysocki
2022-12-07  9:12   ` [PATCH v1 2/2] HID: logitech-hidpp: Add Bluetooth Mouse M336/M337/M535 to unhandled_hidpp_devices[] Rafael J. Wysocki
2022-12-07  9:29     ` Bastien Nocera
2022-12-07  9:47       ` Rafael J. Wysocki
2022-12-07  9:59         ` Bastien Nocera
2022-12-07 10:05         ` Benjamin Tissoires
2022-12-07 10:11           ` Rafael J. Wysocki
2022-12-07 10:19           ` Jiri Kosina
2022-12-07 12:43             ` Bastien Nocera [this message]
2022-12-07 13:00               ` Rafael J. Wysocki
2022-12-07 13:24                 ` Benjamin Tissoires
2022-12-07 13:39                   ` Rafael J. Wysocki
2022-12-07 14:24               ` Bastien Nocera
2022-12-08 13:32                 ` Benjamin Tissoires
2022-12-07  9:48       ` Benjamin Tissoires
2022-12-07  9:59         ` Bastien Nocera
2022-12-08  7:03 ` [Regression] Logitech BT mouse unusable after commit 532223c8ac57 (still in 6.1-rc8) #forregzbot Thorsten Leemhuis
2022-12-09  6:34   ` Thorsten Leemhuis

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=f0ccee0d2f85099c146ee682b25d30c832155fa3.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=rjw@rjwysocki.net \
    /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).