linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: "Filipe Laíns" <lains@riseup.net>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Bastien Nocera" <hadess@hadess.net>,
	"Thorsten Leemhuis" <regressions@leemhuis.info>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] HID: Revert catchall handling of Bluetooth device in hid-logitech-hidpp
Date: Thu, 8 Dec 2022 20:24:53 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2212082019370.9000@cbobk.fhfr.pm> (raw)
In-Reply-To: <20221207142433.1158329-1-benjamin.tissoires@redhat.com>

On Wed, 7 Dec 2022, Benjamin Tissoires wrote:

> We are basically too late in the 6.1 cycle to be able to do anything
> else. Let's revert these 2 patches as we are in a situation where we
> would break too many users.
> 
> We will reintroduce them during the next cycle with proper fixes in the
> driver.

I have now queued this in for-6.1/upstream-fixes and will urgently send it 
to Linus so that we don't have the regression in 6.1 final.

-- 
Jiri Kosina
SUSE Labs


      parent reply	other threads:[~2022-12-08 19:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 14:24 [PATCH v1 0/2] HID: Revert catchall handling of Bluetooth device in hid-logitech-hidpp Benjamin Tissoires
2022-12-07 14:24 ` [PATCH v1 1/2] Revert "HID: logitech-hidpp: Remove special-casing of Bluetooth devices" Benjamin Tissoires
2022-12-07 14:24 ` [PATCH v1 2/2] Revert "HID: logitech-hidpp: Enable HID++ for all the Logitech " Benjamin Tissoires
2022-12-07 16:57 ` [PATCH v1 0/2] HID: Revert catchall handling of Bluetooth device in hid-logitech-hidpp Jiri Kosina
2022-12-08  7:01   ` Thorsten Leemhuis
2022-12-12 17:03   ` Rafael J. Wysocki
2022-12-15 14:48     ` Rafael J. Wysocki
2022-12-08 19:24 ` Jiri Kosina [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=nycvar.YFH.7.76.2212082019370.9000@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hadess@hadess.net \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.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).