From: Guenter Roeck <linux@roeck-us.net>
To: dongfengweixiao@gmail.com, jdelvare@suse.com, linux@roeck-us.ne
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (corsair-cpro) Change dependency from HID to HIDRAW
Date: Wed, 18 Jun 2025 08:41:43 -0700 [thread overview]
Message-ID: <1144cef1-c4af-4fd4-93ae-70a2fcf67f54@roeck-us.net> (raw)
In-Reply-To: <20250618072845.233204-1-dongfengweixiao@gmail.com>
On 6/18/25 00:28, dongfengweixiao@gmail.com wrote:
> From: "Dee.H.Y" <dongfengweixiao@gmail.com>
>
> This patch updates the dependency of the CORSAIR_CPRO driver in the
> hwmon subsystem. Previously, the driver relied on HID, but now it
From Documentation/process/submitting-patches.rst:
Describe your changes in imperative mood, e.g. "make xyzzy do frotz"
instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy
to do frotz", as if you are giving orders to the codebase to change
its behaviour.
What is "previously" ? The driver always used HID_CONNECT_HIDRAW.
Either case, I do not think this patch is warranted. CONFIG_HIDRAW
creates /dev/hidraw for use by applications. This driver does not
need such an application to work. If you disagree, please provide
logs showing that the driver does not work with CONFIG_HIDRAW=n.
Thanks,
Guenter
> depends on HIDRAW. This change is aligned with the implementation
> in the `ccp_probe()` function, where `HID_CONNECT_HIDRAW` is used,
> indicating that the HID raw interface is required for proper operation.
>
> Signed-off-by: Dee.H.Y <dongfengweixiao@gmail.com>
> ---
> drivers/hwmon/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
> index 08a3c863f80a..3f128cacb486 100644
> --- a/drivers/hwmon/Kconfig
> +++ b/drivers/hwmon/Kconfig
> @@ -475,7 +475,7 @@ config SENSORS_CHIPCAP2
>
> config SENSORS_CORSAIR_CPRO
> tristate "Corsair Commander Pro controller"
> - depends on HID
> + depends on HIDRAW
> help
> If you say yes here you get support for the Corsair Commander Pro
> controller.
prev parent reply other threads:[~2025-06-18 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 7:28 dongfengweixiao
2025-06-18 15:41 ` Guenter Roeck [this message]
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=1144cef1-c4af-4fd4-93ae-70a2fcf67f54@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dongfengweixiao@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.ne \
/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
all inboxes | Powered by JetHome®