public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Suraj Patil <surajpatil522@gmail.com>
To: gregkh@linuxfoundation.org
Cc: oneukum@suse.com, stern@rowland.harvard.edu,
	viro@zeniv.linux.org.uk, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Suraj Patil <surajpatil522@gmail.com>
Subject: [PATCH] usb: cdc-wdm: Fix typo in comment
Date: Tue, 11 Mar 2025 17:16:33 +0000	[thread overview]
Message-ID: <20250311171633.469024-1-surajpatil522@gmail.com> (raw)

cdc-wdm: Fix typo in comment

Corrected 'interferring' to 'interfering' in a comment
to improve readability and maintain code quality.
No functional changes.

Signed-off-by: Suraj Patil <surajpatil522@gmail.com>
---
 drivers/usb/class/cdc-wdm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/usb/class/cdc-wdm.c b/drivers/usb/class/cdc-wdm.c
index 86ee39db013f..c5123db416fa 100644
--- a/drivers/usb/class/cdc-wdm.c
+++ b/drivers/usb/class/cdc-wdm.c
@@ -1181,7 +1181,7 @@ static int wdm_probe(struct usb_interface *intf, const struct usb_device_id *id)
  *
  * The subdriver will manage the given interrupt endpoint exclusively
  * and will issue control requests referring to the given intf. It
- * will otherwise avoid interferring, and in particular not do
+ * will otherwise avoid interfering, and in particular not do
  * usb_set_intfdata/usb_get_intfdata on intf.
  *
  * The return value is a pointer to the subdriver's struct usb_driver.
-- 
2.43.0


             reply	other threads:[~2025-03-11 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-11 17:16 Suraj Patil [this message]
2025-03-11 17:36 ` [PATCH] usb: cdc-wdm: Fix typo in comment Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2025-03-11 15:57 Suraj Patil
2025-03-11 16:55 ` Greg KH

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=20250311171633.469024-1-surajpatil522@gmail.com \
    --to=surajpatil522@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=stern@rowland.harvard.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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