From: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
To: jikos@kernel.org, bentiss@kernel.org
Cc: anssi.hannula@gmail.com, oleg@makarenk.ooo,
linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [PATCH v3 0/6] HID: pidff: Compatibility update and new devices
Date: Tue, 11 Feb 2025 15:02:46 +0100 [thread overview]
Message-ID: <20250211140252.702104-1-tomasz.pakula.oficjalny@gmail.com> (raw)
This is a small series based on top of hid.git#for-6.15/pidff.
Add Oleg Makarenko as hid-universal-pidff co-maintainer as he fixed
his email server and will be able to respond to LKML inquiries.
Small compatibility patch for situations, where POOL report haven't
been properly initiated and adding Asetek vendor and 4 of their
wheelbases.
Oleg requested me to change his name order to be in line with
western style.
Signed-off-by: Tomasz Pakuła <tomasz.pakula.oficjalny@gmail.com>
---
Changes in v3:
- Change Oleg's name order on request
Changes in v2:
- Updated comments and code to conform with Linux style guide
- Define 0 duration as FF_INFINITE (PID_INFINITE analog)
- Support device error response from PID_BLOCK_LOAD
- Remove redundant call to pidff_find_special_keys
Tomasz Pakuła (6):
MAINTAINERS: Update hid-universal-pidff entry
HID: pidff: Make sure to fetch pool before checking SIMULTANEOUS_MAX
HID: hid-universal-pidff: Add Asetek wheelbases support
HID: pidff: Comment and code style update
HID: pidff: Support device error response from PID_BLOCK_LOAD
HID: pidff: Remove redundant call to pidff_find_special_keys
MAINTAINERS | 3 +-
drivers/hid/hid-ids.h | 6 ++
drivers/hid/hid-universal-pidff.c | 10 +++-
drivers/hid/usbhid/hid-pidff.c | 98 ++++++++++++++-----------------
4 files changed, 60 insertions(+), 57 deletions(-)
base-commit: 5d98079b2d0186e1f586301a9c00144a669416a8
--
2.48.1
next reply other threads:[~2025-02-11 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 14:02 Tomasz Pakuła [this message]
2025-02-11 14:02 ` [PATCH v3 1/6] MAINTAINERS: Update hid-universal-pidff entry Tomasz Pakuła
2025-02-11 14:02 ` [PATCH v3 2/6] HID: pidff: Make sure to fetch pool before checking SIMULTANEOUS_MAX Tomasz Pakuła
2025-02-11 14:02 ` [PATCH v3 3/6] HID: hid-universal-pidff: Add Asetek wheelbases support Tomasz Pakuła
2025-02-11 14:02 ` [PATCH v3 4/6] HID: pidff: Comment and code style update Tomasz Pakuła
2025-02-11 14:02 ` [PATCH v3 5/6] HID: pidff: Support device error response from PID_BLOCK_LOAD Tomasz Pakuła
2025-02-11 14:02 ` [PATCH v3 6/6] HID: pidff: Remove redundant call to pidff_find_special_keys Tomasz Pakuła
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=20250211140252.702104-1-tomasz.pakula.oficjalny@gmail.com \
--to=tomasz.pakula.oficjalny@gmail.com \
--cc=anssi.hannula@gmail.com \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oleg@makarenk.ooo \
/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).