From: Jiri Kosina <jikos@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing <linux-kernel@vger.kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org
Subject: Re: Strange regression in hid_llogitech_dj (was: Re: Linux 5.2-rc4)
Date: Wed, 12 Jun 2019 10:31:45 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1906121029350.27227@cbobk.fhfr.pm> (raw)
In-Reply-To: <1875376.0DUQQ8o03D@kreacher>
On Wed, 12 Jun 2019, Rafael J. Wysocki wrote:
> It kind of helps, but there is a catch.
>
> hid-logitech-dj is not loaded after a fresh boot, so I need to modprobe it manually and that
> appears to be blocking (apparently indefinitely) until terminated with ^C. But then it turns
> out that hid-logitech-dj is there in the list of modules and it is in use (by usbhid) and the
> mouse works.
My bad, I should've asked you to test with the complete 'for-5.2/fixes'
branch which contains two reverts [1] [2] that should fix this issue as
well.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h=for-5.2/fixes&id=e0b7f9bc0246bc642d1de2ff3ff133730584c956
[2] https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/commit/?h=for-5.2/fixes&id=f9482dabfd1686987cc6044e06ae0e4c05915518
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-06-12 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 3:46 Linux 5.2-rc4 Linus Torvalds
2019-06-09 8:15 ` Bhaskar Chowdhury
2019-06-11 21:53 ` Strange regression in hid_llogitech_dj (was: Re: Linux 5.2-rc4) Rafael J. Wysocki
2019-06-11 22:02 ` Jiri Kosina
2019-06-12 8:24 ` Rafael J. Wysocki
2019-06-12 8:31 ` Jiri Kosina [this message]
2019-06-12 8:51 ` Rafael J. Wysocki
2019-06-12 9:24 ` Jiri Kosina
2019-07-25 10:07 ` [Regression] 5.3-rc1: hid_llogitech_dj does not work Rafael J. Wysocki
2019-07-25 15:50 ` Hans de Goede
2019-07-29 15:49 ` Hans de Goede
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.1906121029350.27227@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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).