From: Sasha Levin <sashal@kernel.org>
To: Aaron Armstrong Skomra <skomra@gmail.com>
Cc: linux-input@vger.kernel.org, jikos@kernel.org,
benjamin.tissoires@redhat.com, ping.cheng@wacom.com,
jason.gerecke@wacom.com,
Aaron Armstrong Skomra <aaron.skomra@wacom.com>,
"# v4 . 3+" <stable@vger.kernel.org>
Subject: Re: [PATCH] HID: wacom: correct misreported EKR ring values
Date: Mon, 19 Aug 2019 13:02:46 -0400 [thread overview]
Message-ID: <20190819170246.GA30205@sasha-vm> (raw)
In-Reply-To: <1566232914-9919-1-git-send-email-aaron.skomra@wacom.com>
On Mon, Aug 19, 2019 at 09:41:54AM -0700, Aaron Armstrong Skomra wrote:
>The EKR ring claims a range of 0 to 71 but actually reports
>values 1 to 72. The ring is used in relative mode so this
>change should not affect users.
>
>Signed-off-by: Aaron Armstrong Skomra <aaron.skomra@wacom.com>
>Fixes: 72b236d60218f ("HID: wacom: Add support for Express Key Remote.")
>Cc: <stable@vger.kernel.org> # v4.3+
>Reviewed-by: Ping Cheng <ping.cheng@wacom.com>
>Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com>
>---
>Patch specifically targeted to v4.9.189
Is this not a problem upstream as well? Why not?
If it is, this patch will need to go upstream first, and then it'll get
to stable branches from there.
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-08-19 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 16:41 [PATCH] HID: wacom: correct misreported EKR ring values Aaron Armstrong Skomra
2019-08-19 17:02 ` Sasha Levin [this message]
[not found] ` <CAEoswT3mvABD7T_0WkwrAOe1PHO62jZ63tUb2UBQLm_Tqu-guw@mail.gmail.com>
2019-08-19 19:03 ` Sasha Levin
[not found] <20190817181109.33F1B2173B@mail.kernel.org>
2019-08-19 17:20 ` Aaron Armstrong Skomra
-- strict thread matches above, loose matches on Subject: below --
2019-08-16 19:00 Aaron Armstrong Skomra
2019-08-20 8:43 ` 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=20190819170246.GA30205@sasha-vm \
--to=sashal@kernel.org \
--cc=aaron.skomra@wacom.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jason.gerecke@wacom.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=ping.cheng@wacom.com \
--cc=skomra@gmail.com \
--cc=stable@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