From: sashiko-bot@kernel.org
To: "Shihuang Liu" <shlomojune6@gmail.com>, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 RESEND 5/6] Input: tablet - use usb_make_subpath()
Date: Thu, 22 Oct 2026 07:12:44 +0000 [thread overview]
Message-ID: <sashiko-outbox-181116@kernel.org> (raw)
In-Reply-To: <20261022070929.20820-6-shlomojune6@gmail.com>
> The acecad, aiptek, hanwang, kbtab and pegasus_notetaker drivers build
> their input device physical paths by appending "/input0" with strlcat()
> after usb_make_path().
>
> In preparation for removing the deprecated strlcat() API [1], replace
> each pair of calls with usb_make_subpath(). The helper formats the USB
> path and the "input0" subpath in one call, avoiding a separate buffer
> scan and append operation.
>
> Link: https://github.com/KSPP/linux/issues/370 [1]
> Signed-off-by: Shihuang Liu <shlomojune6@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261022070929.20820-1-shlomojune6@gmail.com?part=5
next prev parent reply other threads:[~2026-10-22 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261021123146.17202-1-shlomojune6@gmail.com>
2026-10-22 7:09 ` [PATCH v2 RESEND 0/6] USB: add usb_make_subpath() to replace strlcat() in input drivers Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 1/6] USB: add usb_make_subpath() for formatted device subpaths Shihuang Liu
2026-10-22 7:14 ` sashiko-bot
2026-10-22 7:09 ` [PATCH v2 RESEND 2/6] Input: joystick - use usb_make_subpath() Shihuang Liu
2026-10-22 7:12 ` sashiko-bot
2026-10-22 7:09 ` [PATCH v2 RESEND 3/6] Input: misc " Shihuang Liu
2026-10-22 7:12 ` sashiko-bot
2026-10-22 7:09 ` [PATCH v2 RESEND 4/6] Input: mouse " Shihuang Liu
2026-10-22 7:12 ` sashiko-bot
2026-10-22 7:09 ` [PATCH v2 RESEND 5/6] Input: tablet " Shihuang Liu
2026-10-22 7:12 ` sashiko-bot [this message]
2026-10-22 7:09 ` [PATCH v2 RESEND 6/6] Input: touchscreen " Shihuang Liu
2026-10-22 7:12 ` sashiko-bot
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=sashiko-outbox-181116@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shlomojune6@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