From: Greg KH <greg@kroah.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-usb@vger.kernel.org
Subject: Re: [Bug 211325] New: usbhid.mousepoll kernel cmd option not working
Date: Sun, 24 Jan 2021 09:14:11 +0100 [thread overview]
Message-ID: <YA0sU+5gxO7oTy45@kroah.com> (raw)
In-Reply-To: <bug-211325-208809@https.bugzilla.kernel.org/>
On Sun, Jan 24, 2021 at 04:35:13AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=211325
>
> Bug ID: 211325
> Summary: usbhid.mousepoll kernel cmd option not working
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.11-rc3
> Hardware: ARM
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: low
> Priority: P1
> Component: USB
> Assignee: drivers_usb@kernel-bugs.kernel.org
> Reporter: mathias.steiger@gmail.com
> Regression: No
>
> It doesn't matter what value I use, it is treated as if unset (i.e. "0").
Please email the linux-input@vger.kernel.org list about this.
next prev parent reply other threads:[~2021-01-24 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 4:35 [Bug 211325] New: usbhid.mousepoll kernel cmd option not working bugzilla-daemon
2021-01-24 8:14 ` Greg KH [this message]
2021-01-24 8:14 ` [Bug 211325] " bugzilla-daemon
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=YA0sU+5gxO7oTy45@kroah.com \
--to=greg@kroah.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.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