Linux Input/HID development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rong Zhang" <i@rong.moe>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH v2 7/9] HID: Add hid-plugin framework for loadable plugin modules
Date: Wed, 11 Nov 2026 00:25:56 +0000	[thread overview]
Message-ID: <sashiko-outbox-208018@kernel.org> (raw)
In-Reply-To: <20261110-hid-haptic-kmod-v2-7-b835a067cb62@rong.moe>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] HID: hid-plugin: missing Return section in hid_plugin_register()
  kernel-doc
--

commit ea30651fd5d31e4684e4f118c37b9199cf1158fc
Author: Rong Zhang <i@rong.moe>

HID: Add hid-plugin framework for loadable plugin modules

This commit introduces a hid-plugin framework that allows HID drivers to
request optional loadable or builtin plugin modules via RCU and module
reference counting.

Link: https://lore.kernel.org/linux-input/auypydfkhx2eg7vp764way4batdilzc35inqda3exwzs3tk3ff@oagat6g46zto/

> diff --git a/drivers/hid/hid-plugin.h b/drivers/hid/hid-plugin.h
> new file mode 100644
> index 0000000000000..4038325c51a08
> --- /dev/null
> +++ b/drivers/hid/hid-plugin.h

[ ... ]

> +/**
> + * hid_plugin_register() - Register an HID plugin.
> + * @id: Unique ID of @plugin
> + * @plugin: Pointer to the HID plugin
> + */
> +static __always_inline int hid_plugin_register(enum hid_plugin_id id, struct hid_plugin *plugin)
> +{
> +	BUILD_BUG_ON(!hid_plugin_enabled(id));
> +
> +	return __hid_plugin_register(id, plugin);
> +}

[Severity: Low]
The kernel-doc comment for hid_plugin_register() omits a Return: section,
which causes a kernel-doc warning when building with W=1.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-hid-haptic-kmod-v2-0-b835a067cb62@rong.moe?part=7

  reply	other threads:[~2026-11-11  0:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 19:49 [PATCH v2 0/9] HID: Add hid-plugin framework & convert haptic into a plugin Rong Zhang
2026-11-09 19:49 ` [PATCH v2 1/9] HID: haptic: Fix use-after-free when draining workqueue Rong Zhang
2026-11-09 19:49 ` [PATCH v2 2/9] HID: haptic: Get rid of input_ff_destroy() in error paths Rong Zhang
2026-11-09 19:49 ` [PATCH v2 3/9] HID: haptic, multitouch: Check haptic prerequisite properly Rong Zhang
2026-11-09 19:49 ` [PATCH v2 4/9] HID: haptic, multitouch: Fix haptic device double-free and unnecessary allocation Rong Zhang
2026-11-11  0:06   ` sashiko-bot
2026-11-09 19:49 ` [PATCH v2 5/9] HID: haptic: Postpone GET_REPORT to init Rong Zhang
2026-11-09 19:49 ` [PATCH v2 6/9] HID: haptic: Convert simple methods into static inline ones Rong Zhang
2026-11-09 19:49 ` [PATCH v2 7/9] HID: Add hid-plugin framework for loadable plugin modules Rong Zhang
2026-11-11  0:25   ` sashiko-bot [this message]
2026-11-09 19:49 ` [PATCH v2 8/9] HID: haptic: Convert into a loadable plugin module Rong Zhang
2026-11-09 19:49 ` [PATCH v2 9/9] HID: haptic: Remove stubs in favor of inlined dead code elimination Rong Zhang
2026-11-11  0:45   ` sashiko-bot
2026-11-11 12:09     ` Rong Zhang

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-208018@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=i@rong.moe \
    --cc=linux-input@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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