2023-02-16 01:35:44

by zhounan

[permalink] [raw]
Subject: [PATCH v2] usb: fix some spelling mistakes in comment of gadget

usb: Fix spelling mistake in comments of gadget.

Signed-off-by: Zhou nan <[email protected]>
---
v2:
- Modify the title and description text.
---
drivers/usb/gadget/udc/fsl_udc_core.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/usb/gadget/udc/fsl_udc_core.c b/drivers/usb/gadget/udc/fsl_udc_core.c
index a67873a074b7..da876d09fc01 100644
--- a/drivers/usb/gadget/udc/fsl_udc_core.c
+++ b/drivers/usb/gadget/udc/fsl_udc_core.c
@@ -471,7 +471,7 @@ static int dr_ep_get_stall(unsigned char ep_num, unsigned char dir)
********************************************************************/

/*------------------------------------------------------------------
-* struct_ep_qh_setup(): set the Endpoint Capabilites field of QH
+* struct_ep_qh_setup(): set the Endpoint Capabilities field of QH
* @zlt: Zero Length Termination Select (1: disable; 0: enable)
* @mult: Mult field
------------------------------------------------------------------*/
@@ -483,7 +483,7 @@ static void struct_ep_qh_setup(struct fsl_udc *udc, unsigned char ep_num,
struct ep_queue_head *p_QH = &udc->ep_qh[2 * ep_num + dir];
unsigned int tmp = 0;

- /* set the Endpoint Capabilites in QH */
+ /* set the Endpoint Capabilities in QH */
switch (ep_type) {
case USB_ENDPOINT_XFER_CONTROL:
/* Interrupt On Setup (IOS). for control ep */
@@ -593,7 +593,7 @@ static int fsl_ep_enable(struct usb_ep *_ep,
ep->stopped = 0;

/* Controller related setup */
- /* Init EPx Queue Head (Ep Capabilites field in QH
+ /* Init EPx Queue Head (Ep Capabilities field in QH
* according to max, zlt, mult) */
struct_ep_qh_setup(udc, (unsigned char) ep_index(ep),
(unsigned char) ((desc->bEndpointAddress & USB_DIR_IN)
@@ -1361,7 +1361,7 @@ static void ch9getstatus(struct fsl_udc *udc, u8 request_type, u16 value,
udc->ep0_dir = USB_DIR_IN;
/* Borrow the per device status_req */
req = udc->status_req;
- /* Fill in the reqest structure */
+ /* Fill in the request structure */
*((u16 *) req->req.buf) = cpu_to_le16(tmp);

req->ep = ep;
--
2.27.0



2023-02-16 02:20:23

by Randy Dunlap

[permalink] [raw]
Subject: Re: [PATCH v2] usb: fix some spelling mistakes in comment of gadget



On 2/15/23 17:35, Zhou nan wrote:
> usb: Fix spelling mistake in comments of gadget.
>
> Signed-off-by: Zhou nan <[email protected]>

Acked-by: Randy Dunlap <[email protected]>

Thanks.

> ---
> v2:
> - Modify the title and description text.
> ---
> drivers/usb/gadget/udc/fsl_udc_core.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)


--
~Randy

2023-02-16 11:46:07

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH v2] usb: fix some spelling mistakes in comment of gadget

On Wed, Feb 15, 2023 at 05:35:35PM -0800, Zhou nan wrote:
> usb: Fix spelling mistake in comments of gadget.
>
> Signed-off-by: Zhou nan <[email protected]>
> ---

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- You did not specify a description of why the patch is needed, or
possibly, any description at all, in the email body. Please read the
section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what is needed in
order to properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg,
and everyone else, to know what this patch is all about. Please read
the section entitled "The canonical patch format" in the kernel file,
Documentation/process/submitting-patches.rst for what a proper
Subject: line should look like.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot