From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Jiri Kosina <jikos@kernel.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
mad skateman <madskateman@gmail.com>,
linux-input@vger.kernel.org,
Christian Zigotzky <info@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
anpatel@nvidia.com
Subject: Re: [PASEMI] Nemo board doesn't reboot anymore after the commit "HID: usbhid: Add ALWAYS_POLL quirk for some mice"
Date: Tue, 17 Jan 2023 14:51:43 +0100 [thread overview]
Message-ID: <aafbda4b-3a1a-cf7d-0a29-ba0b8b4adc4e@xenosoft.de> (raw)
In-Reply-To: <nycvar.YFH.7.76.2301061540530.1734@cbobk.fhfr.pm>
On 06 January 2023 at 03:41 pm, Jiri Kosina wrote:
> On Fri, 6 Jan 2023, Christian Zigotzky wrote:
>
>> Hello,
>>
>> The reboot issue is still present in the RC2 of kernel 6.2. We still need the
>> usbhid.patch. [1]
>>
>> Please check the bad commit. [2]
> Ankit,
>
> have you tested with all the devices that you added the quirk for in your
> original patch?
>
> Unless I hear otherwise, I will just drop
> the quirk for USB_DEVICE_ID_CHERRY_MOUSE_000C before this gets clarified.
>
> Thanks,
>
The issue also affects the RC4.
-- Christian
next prev parent reply other threads:[~2023-01-17 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 10:42 [PASEMI] Nemo board doesn't reboot anymore after the commit "HID: usbhid: Add ALWAYS_POLL quirk for some mice" Christian Zigotzky
2022-12-22 11:24 ` [PASEMI] Nemo board doesn't reboot anymore after the commit "HID: usbhid: Add ALWAYS_POLL quirk for some mice" #forregzbot Thorsten Leemhuis
2023-01-30 15:21 ` Linux kernel regression tracking (#update)
2023-01-06 14:29 ` [PASEMI] Nemo board doesn't reboot anymore after the commit "HID: usbhid: Add ALWAYS_POLL quirk for some mice" Christian Zigotzky
2023-01-06 14:41 ` Jiri Kosina
2023-01-17 13:51 ` Christian Zigotzky [this message]
2023-01-17 14:46 ` Jiri Kosina
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=aafbda4b-3a1a-cf7d-0a29-ba0b8b4adc4e@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=anpatel@nvidia.com \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
/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).