From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Harry Cutts <hcutts@chromium.org>,
linux-input <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jiri.kosina@suse.cz>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 1/3] Add the `REL_WHEEL_HI_RES` event code
Date: Thu, 23 Aug 2018 12:01:24 -0700 [thread overview]
Message-ID: <20180823190124.GB53155@dtor-ws> (raw)
In-Reply-To: <20180823185722.GA24777@bombadil.infradead.org>
On Thu, Aug 23, 2018 at 11:57:22AM -0700, Matthew Wilcox wrote:
> On Thu, Aug 23, 2018 at 11:30:55AM -0700, Harry Cutts wrote:
> > + - If a vertical scroll wheel supports high-resolution scrolling, this code
> > + will be emitted in addition to REL_WHEEL. The value is the (approximate)
> > + distance travelled by the user's finger, in 256ths of a millimeter.
>
> Is it too late to change this to an actual unit like micrometres?
No love for imperial roots? Sure, micrometers would work too I think.
--
Dmitry
next prev parent reply other threads:[~2018-08-23 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 18:30 [PATCH 0/3] Add support for high-resolution scrolling on Logitech mice Harry Cutts
2018-08-23 18:30 ` [PATCH 1/3] Add the `REL_WHEEL_HI_RES` event code Harry Cutts
2018-08-23 18:42 ` Dmitry Torokhov
2018-08-23 18:57 ` Matthew Wilcox
2018-08-23 19:01 ` Dmitry Torokhov [this message]
2018-08-28 9:02 ` Jiri Kosina
2018-08-28 17:49 ` Harry Cutts
2018-08-23 18:30 ` [PATCH 2/3] Create a utility class for counting scroll events Harry Cutts
2018-08-23 18:30 ` [PATCH 3/3] Enable high-resolution scrolling on Logitech mice Harry Cutts
2018-08-28 8:47 ` Benjamin Tissoires
[not found] ` <CA+jURcvguwXAVnpQ9+84QQOaJG74oeV8U4zzM1X0UabaY5DJBQ@mail.gmail.com>
2018-08-30 7:18 ` Benjamin Tissoires
2018-08-30 20:37 ` Harry Cutts
[not found] ` <CAE7qMrrBdZSg1P+JTr9SA5a1ui-zdAmsg6pE-B1N5La_1WwvHw@mail.gmail.com>
2018-08-31 9:14 ` Nestor Lopez Casado
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=20180823190124.GB53155@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=corbet@lwn.net \
--cc=hcutts@chromium.org \
--cc=jiri.kosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.