All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Cong <cong.yi@linux.dev>
To: gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	yicong@kylinos.cn
Subject: [PATCH] usb: linux/usb.h: Correct the description of the usb_device_driver member
Date: Mon,  1 Dec 2025 16:53:09 +0800	[thread overview]
Message-ID: <20251201085309.103379-1-cong.yi@linux.dev> (raw)

From: Yi Cong <yicong@kylinos.cn>

In the current kernel USB device driver code, only the name field is
required to be provided; all other fields are optional.
Use the command grep -rnw "struct usb_device_driver" to inspect
how specific drivers are declared.

Correct this part of the description.

Signed-off-by: Yi Cong <yicong@kylinos.cn>
---
 include/linux/usb.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/include/linux/usb.h b/include/linux/usb.h
index e85105939af8e..fbfcc70b07fbe 100644
--- a/include/linux/usb.h
+++ b/include/linux/usb.h
@@ -1295,8 +1295,7 @@ struct usb_driver {
  *	resume and suspend functions will be called in addition to the driver's
  *	own, so this part of the setup does not need to be replicated.
  *
- * USB drivers must provide all the fields listed above except driver,
- * match, and id_table.
+ * USB device drivers must provide a name, other driver fields are optional.
  */
 struct usb_device_driver {
 	const char *name;
-- 
2.25.1


             reply	other threads:[~2025-12-01  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  8:53 Yi Cong [this message]
2025-12-01 15:14 ` [PATCH] usb: linux/usb.h: Correct the description of the usb_device_driver member Alan Stern
2025-12-02  6:59   ` Yi Cong
2025-12-02  9:00     ` 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=20251201085309.103379-1-cong.yi@linux.dev \
    --to=cong.yi@linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=yicong@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.