From: Jiri Kosina <jikos@kernel.org>
To: "José Expósito" <jose.exposito89@gmail.com>
Cc: benjamin.tissoires@redhat.com, spbnick@gmail.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-5.18/uclogic 0/9] DIGImend patches, part II
Date: Tue, 1 Mar 2022 15:29:21 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2203011529020.11721@cbobk.fhfr.pm> (raw)
In-Reply-To: <20220219100157.41920-1-jose.exposito89@gmail.com>
On Sat, 19 Feb 2022, José Expósito wrote:
> Hi everyone,
>
> This series is a follow up to [1], kindly reviewed and applied
> by Jiří in hid.git#for-5.18/uclogic.
>
> It might look a little bit longer than desired, but most of the
> patches are code simplification and refactoring in preparation
> for the last patch which adds support for multiple frame input
> devices.
>
> Thank you very much in advance to maintainers for reviewing it,
> José Expósito
>
> [1] https://lore.kernel.org/linux-input/nycvar.YFH.7.76.2202161642180.11721@cbobk.fhfr.pm/T/
>
> Nikolai Kondrashov (9):
> HID: uclogic: Remove pen usage masking
> HID: uclogic: Replace pen_frame_flag with subreport_list
> HID: uclogic: Switch to matching subreport bytes
> HID: uclogic: Specify total report size to buttonpad macro
> HID: uclogic: Use different constants for frame report IDs
> HID: uclogic: Use "frame" instead of "buttonpad"
> HID: uclogic: Put version first in rdesc namespace
> HID: uclogic: Define report IDs before their descriptors
> HID: uclogic: Support multiple frame input devices
>
> drivers/hid/hid-uclogic-core.c | 79 +++++++------
> drivers/hid/hid-uclogic-params.c | 195 ++++++++++++++-----------------
> drivers/hid/hid-uclogic-params.h | 86 +++++++-------
> drivers/hid/hid-uclogic-rdesc.c | 53 ++++-----
> drivers/hid/hid-uclogic-rdesc.h | 38 +++---
> 5 files changed, 221 insertions(+), 230 deletions(-)
Now queued in hid.git#for-5.18/uclogic.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2022-03-01 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 10:01 [PATCH for-5.18/uclogic 0/9] DIGImend patches, part II José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 1/9] HID: uclogic: Remove pen usage masking José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 2/9] HID: uclogic: Replace pen_frame_flag with subreport_list José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 3/9] HID: uclogic: Switch to matching subreport bytes José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 4/9] HID: uclogic: Specify total report size to buttonpad macro José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 5/9] HID: uclogic: Use different constants for frame report IDs José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 6/9] HID: uclogic: Use "frame" instead of "buttonpad" José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 7/9] HID: uclogic: Put version first in rdesc namespace José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 8/9] HID: uclogic: Define report IDs before their descriptors José Expósito
2022-02-19 10:01 ` [PATCH for-5.18/uclogic 9/9] HID: uclogic: Support multiple frame input devices José Expósito
2022-03-01 14:29 ` Jiri Kosina [this message]
2022-03-01 14:32 ` [PATCH for-5.18/uclogic 0/9] DIGImend patches, part II Nikolai Kondrashov
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.2203011529020.11721@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spbnick@gmail.com \
/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).