From: Jonathan Cameron <jic23@kernel.org>
To: Chelsy Ratnawat <chelsyratnawat2001@gmail.com>
Cc: jikos@kernel.org, bentiss@kernel.org,
srinivas.pandruvada@linux.intel.com, dlechner@baylibre.com,
linux-input@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] HID: sensor-hub: Fix typo and improve documentation for sensor_hub_remove_callback()
Date: Sun, 4 May 2025 17:49:41 +0100 [thread overview]
Message-ID: <20250504174941.1390b21b@jic23-huawei> (raw)
In-Reply-To: <20250502003655.1943000-1-chelsyratnawat2001@gmail.com>
On Thu, 1 May 2025 17:36:55 -0700
Chelsy Ratnawat <chelsyratnawat2001@gmail.com> wrote:
> Fixed a typo in "registered" and improved grammar for better readability
> and consistency with kernel-doc standards. No functional changes.
>
> Signed-off-by: Chelsy Ratnawat <chelsyratnawat2001@gmail.com>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
> ---
Even though trivial reason for resend, this is v3.
Posting it as v2 confuses some tooling such as b4.
I manually grabbed the right patch and applied.
Thanks,
Jonathan
> Changes in v2:
> - Improved the kernel-doc comment for sensor_hub_remove_callback().
> - Changed "Gyro" to "gyro".
> - Changed "usage ID" to "usage_id" for consistency with kernel-doc
> style.
> - Updated the comment to state that only one callback can be removed
> per (usage_id, hsdev) pair.
>
> include/linux/hid-sensor-hub.h | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/hid-sensor-hub.h b/include/linux/hid-sensor-hub.h
> index c27329e2a5ad..0f9f7df865db 100644
> --- a/include/linux/hid-sensor-hub.h
> +++ b/include/linux/hid-sensor-hub.h
> @@ -128,12 +128,13 @@ int sensor_hub_register_callback(struct hid_sensor_hub_device *hsdev,
> struct hid_sensor_hub_callbacks *usage_callback);
>
> /**
> -* sensor_hub_remove_callback() - Remove client callbacks
> +* sensor_hub_remove_callback() - Remove client callback
> * @hsdev: Hub device instance.
> -* @usage_id: Usage id of the client (E.g. 0x200076 for Gyro).
> +* @usage_id: Usage id of the client (e.g. 0x200076 for gyro).
> *
> -* If there is a callback registred, this call will remove that
> -* callbacks, so that it will stop data and event notifications.
> +* Removes a previously registered callback for the given usage_id
> +* and hsdev. Once removed, the client will no longer receive data or
> +* event notifications.
> */
> int sensor_hub_remove_callback(struct hid_sensor_hub_device *hsdev,
> u32 usage_id);
prev parent reply other threads:[~2025-05-04 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 18:23 [PATCH] HID: sensor-hub: Fix typo and improve documentation for sensor_hub_remove_callback() Chelsy Ratnawat
2025-04-30 19:17 ` David Lechner
2025-05-01 23:21 ` srinivas pandruvada
[not found] ` <CAOeBcHOw6CHbY6W+wAWvYsm_CGRMCgt_BLSV65X=rnhuU1r1hw@mail.gmail.com>
2025-05-01 23:52 ` David Lechner
2025-05-01 23:19 ` [PATCH v2] " Chelsy Ratnawat
2025-05-01 23:30 ` David Lechner
2025-05-02 0:36 ` Chelsy Ratnawat
2025-05-04 16:49 ` Jonathan Cameron [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=20250504174941.1390b21b@jic23-huawei \
--to=jic23@kernel.org \
--cc=bentiss@kernel.org \
--cc=chelsyratnawat2001@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jikos@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.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