Linux USB
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Hemanth Selam" <hemanth.selam@gmail.com>,
	"Jiri Kosina" <jikos@kernel.org>,
	"Benjamin Tissoires" <bentiss@kernel.org>,
	"Filipe Laíns" <lains@riseup.net>,
	"Stefan Achatz" <erazor_de@users.sourceforge.net>,
	"Srinivas Pandruvada" <srinivas.pandruvada@linux.intel.com>,
	"Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>,
	"Oleg Makarenko" <oleg@makarenk.ooo>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	 linux-usb@vger.kernel.org
Subject: Re: [PATCH] hid: fix typos in comments
Date: Fri, 04 Sep 2026 14:06:55 +0200	[thread overview]
Message-ID: <4110b6590ad1dbff92e28539d99376d2ea99c50b.camel@hadess.net> (raw)
In-Reply-To: <20260904114444.28585-1-hemanth.selam@gmail.com>

On Fri, 2026-09-04 at 17:14 +0530, Hemanth Selam wrote:
> Fix typos in comments, reported by scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt.  Only touches comments, no
> code
> changes.
> 
> Assisted-by: Cursor:claude-opus-5
> Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
> ---
>  drivers/hid/hid-appleir.c                        | 2 +-
>  drivers/hid/hid-logitech-dj.c                    | 2 +-
>  drivers/hid/hid-logitech-hidpp.c                 | 4 ++--

For those 3 files above:

Reviewed-by: Bastien Nocera <hadess@hadess.net>

>  drivers/hid/hid-roccat-kone.c                    | 2 +-
>  drivers/hid/hid-roccat-kone.h                    | 2 +-
>  drivers/hid/hid-speedlink.c                      | 2 +-
>  drivers/hid/intel-ish-hid/ishtp-hid-client.c     | 2 +-
>  drivers/hid/intel-ish-hid/ishtp/client-buffers.c | 2 +-
>  drivers/hid/usbhid/hid-pidff.c                   | 2 +-
>  9 files changed, 10 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/hid/hid-appleir.c b/drivers/hid/hid-appleir.c
> index adaa44a858ed..649ee5d8fe1e 100644
> --- a/drivers/hid/hid-appleir.c
> +++ b/drivers/hid/hid-appleir.c
> @@ -118,7 +118,7 @@ struct appleir {
>  static int get_key(int data)
>  {
>  	/*
> -	 * The key is coded accross bits 2..9:
> +	 * The key is coded across bits 2..9:
>  	 *
>  	 * 0x00 or 0x01 (        )	key:  0		->
> KEY_RESERVED
>  	 * 0x02 or 0x03 (  menu  )	key:  1		->
> KEY_MENU
> diff --git a/drivers/hid/hid-logitech-dj.c b/drivers/hid/hid-
> logitech-dj.c
> index 1d619d2345e1..51aaee2e29e3 100644
> --- a/drivers/hid/hid-logitech-dj.c
> +++ b/drivers/hid/hid-logitech-dj.c
> @@ -620,7 +620,7 @@ static const char hidpp_descriptor[] = {
>   *
>   * Right now, RF report types have the same report types (or report
> id's)
>   * than the hid report created from those RF reports. In the future
> - * this doesnt have to be true.
> + * this doesn't have to be true.
>   *
>   * For instance, RF report type 0x01 which has a size of 8 bytes,
> corresponds
>   * to hid report id 0x01, this is standard keyboard. Same thing
> applies to mice
> diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-
> logitech-hidpp.c
> index 1504de32b1c8..5273a5a7e7a0 100644
> --- a/drivers/hid/hid-logitech-hidpp.c
> +++ b/drivers/hid/hid-logitech-hidpp.c
> @@ -110,7 +110,7 @@ MODULE_PARM_DESC(disable_tap_to_click,
>   * where as most newer devices use the FAP protocol. Both protocols
> are
>   * compatible with the underlying transport, which could be usb,
> Unifiying, or
>   * bluetooth. The message lengths are defined by the hid vendor
> specific report
> - * descriptor for the HIDPP_SHORT report type (total message lenth 7
> bytes) and
> + * descriptor for the HIDPP_SHORT report type (total message length
> 7 bytes) and
>   * the HIDPP_LONG report type (total message length 20 bytes)
>   *
>   * The RAP protocol uses both report types, whereas the FAP only
> uses HIDPP_LONG
> @@ -3354,7 +3354,7 @@ static int m560_input_mapping(struct hid_device
> *hdev, struct hid_input *hi,
>  /*
>   * The Logitech K400 keyboard has an embedded touchpad which is seen
>   * as a mouse from the OS point of view. There is a hardware
> shortcut to disable
> - * tap-to-click but the setting is not remembered accross reset,
> annoying some
> + * tap-to-click but the setting is not remembered across reset,
> annoying some
>   * users.
>   *
>   * We can toggle this feature from the host by using the feature
> 0x6010:
> diff --git a/drivers/hid/hid-roccat-kone.c b/drivers/hid/hid-roccat-
> kone.c
> index 3dae9eaa0b6f..5b84435cbe8f 100644
> --- a/drivers/hid/hid-roccat-kone.c
> +++ b/drivers/hid/hid-roccat-kone.c
> @@ -842,7 +842,7 @@ static void kone_report_to_chrdev(struct
> kone_device const *kone,
>  
>  /*
>   * Is called for keyboard- and mousepart.
> - * Only mousepart gets informations about special events in its
> extended event
> + * Only mousepart gets information about special events in its
> extended event
>   * structure.
>   */
>  static int kone_raw_event(struct hid_device *hdev, struct hid_report
> *report,
> diff --git a/drivers/hid/hid-roccat-kone.h b/drivers/hid/hid-roccat-
> kone.h
> index 65c800e3addc..13de9f14dc1e 100644
> --- a/drivers/hid/hid-roccat-kone.h
> +++ b/drivers/hid/hid-roccat-kone.h
> @@ -165,7 +165,7 @@ enum kone_mouse_events {
>  	/* osd events are thought to be display on screen */
>  	kone_mouse_event_osd_dpi = 0xa0,
>  	kone_mouse_event_osd_profile = 0xb0,
> -	/* TODO clarify meaning and occurence of
> kone_mouse_event_calibration */
> +	/* TODO clarify meaning and occurrence of
> kone_mouse_event_calibration */
>  	kone_mouse_event_calibration = 0xc0,
>  	kone_mouse_event_call_overlong_macro = 0xe0,
>  	kone_mouse_event_multimedia = 0xe1,
> diff --git a/drivers/hid/hid-speedlink.c b/drivers/hid/hid-
> speedlink.c
> index 22ee078c42c6..3196bb85ccc2 100644
> --- a/drivers/hid/hid-speedlink.c
> +++ b/drivers/hid/hid-speedlink.c
> @@ -44,7 +44,7 @@ static int speedlink_event(struct hid_device *hdev,
> struct hid_field *field,
>  {
>  	/* No other conditions due to usage_table. */
>  
> -	/* This fixes the "jumpy" cursor occuring due to invalid
> events sent
> +	/* This fixes the "jumpy" cursor occurring due to invalid
> events sent
>  	 * by the device. Some devices only send them with
> value==+256, others
>  	 * don't. However, catching abs(value)>=256 is restrictive
> enough not
>  	 * to interfere with devices that were bug-free (has been
> tested).
> diff --git a/drivers/hid/intel-ish-hid/ishtp-hid-client.c
> b/drivers/hid/intel-ish-hid/ishtp-hid-client.c
> index ec5e8afe77bd..acfe25fd8b23 100644
> --- a/drivers/hid/intel-ish-hid/ishtp-hid-client.c
> +++ b/drivers/hid/intel-ish-hid/ishtp-hid-client.c
> @@ -631,7 +631,7 @@ static int ishtp_get_report_descriptor(struct
> ishtp_cl *hid_ishtp_cl,
>   * @hid_ishtp_cl:	ISHTP client instance
>   * @reset:		true if called for init after reset
>   *
> - * This function complete the initializtion of the client. The
> summary of
> + * This function complete the initialization of the client. The
> summary of
>   * processing:
>   * - Send request to enumerate the hid clients
>   *	Get the HID descriptor for each enumearated device
> diff --git a/drivers/hid/intel-ish-hid/ishtp/client-buffers.c
> b/drivers/hid/intel-ish-hid/ishtp/client-buffers.c
> index 45ddc9a047bc..6bac76249437 100644
> --- a/drivers/hid/intel-ish-hid/ishtp/client-buffers.c
> +++ b/drivers/hid/intel-ish-hid/ishtp/client-buffers.c
> @@ -177,7 +177,7 @@ void ishtp_io_rb_free(struct ishtp_cl_rb *rb)
>   *
>   * Allocate and initialize request block
>   *
> - * Return: Allocted IO request block pointer
> + * Return: Allocated IO request block pointer
>   */
>  struct ishtp_cl_rb *ishtp_io_rb_init(struct ishtp_cl *cl)
>  {
> diff --git a/drivers/hid/usbhid/hid-pidff.c b/drivers/hid/usbhid/hid-
> pidff.c
> index 22951b7ecd17..82150a72506b 100644
> --- a/drivers/hid/usbhid/hid-pidff.c
> +++ b/drivers/hid/usbhid/hid-pidff.c
> @@ -20,7 +20,7 @@
>  #define	PID_EFFECTS_MAX		64
>  #define	PID_INFINITE		U16_MAX
>  
> -/* Linux Force Feedback API uses miliseconds as time unit */
> +/* Linux Force Feedback API uses milliseconds as time unit */
>  #define FF_TIME_EXPONENT	-3
>  #define FF_INFINITE		0
>  

      reply	other threads:[~2026-09-04 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 11:44 [PATCH] hid: fix typos in comments Hemanth Selam
2026-09-04 12:06 ` Bastien Nocera [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=4110b6590ad1dbff92e28539d99376d2ea99c50b.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=bentiss@kernel.org \
    --cc=erazor_de@users.sourceforge.net \
    --cc=hemanth.selam@gmail.com \
    --cc=jikos@kernel.org \
    --cc=lains@riseup.net \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oleg@makarenk.ooo \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tomasz.pakula.oficjalny@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