From: Greg KH <gregkh@linuxfoundation.org>
To: Jonathan Velez <jonvelez12345@gmail.com>
Cc: Thinh.Nguyen@synopsys.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: usb: dwc3: add documentation of 'sg' field in dwc3_request struct
Date: Sun, 18 May 2025 13:57:17 +0200 [thread overview]
Message-ID: <2025051804-postage-tremble-d9d1@gregkh> (raw)
In-Reply-To: <20250518113330.8976-1-jonvelez12345@gmail.com>
On Sun, May 18, 2025 at 11:33:30AM +0000, Jonathan Velez wrote:
> core: Add documentation of "sg" field in the dwc3_request struct.
>
> Signed-off-by: Jonathan Velez <jonvelez12345@gmail.com>
> ---
> drivers/usb/dwc3/core.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> index f11570c8ffd0..bb140dde07d6 100644
> --- a/drivers/usb/dwc3/core.h
> +++ b/drivers/usb/dwc3/core.h
> @@ -942,6 +942,7 @@ struct dwc3_hwparams {
> * @request: struct usb_request to be transferred
> * @list: a list_head used for request queueing
> * @dep: struct dwc3_ep owning this request
> + * @sg: pointer to the scatter-gather list for transfers
> * @start_sg: pointer to the sg which should be queued next
> * @num_pending_sgs: counter to pending sgs
> * @remaining: amount of data remaining
> --
> 2.43.0
>
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:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/process/submitting-patches.rst for what
needs to be done here to properly describe this.
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
next prev parent reply other threads:[~2025-05-18 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-18 11:33 [PATCH] docs: usb: dwc3: add documentation of 'sg' field in dwc3_request struct Jonathan Velez
2025-05-18 11:57 ` Greg KH [this message]
2025-05-18 11:58 ` Greg KH
2025-05-18 12:08 ` Jonathan Velez
2025-05-18 12:11 ` Greg KH
2025-05-18 12:19 ` Jonathan Velez
-- strict thread matches above, loose matches on Subject: below --
2025-05-18 11:48 Jonathan Velez
2025-05-16 23:54 Jonathan Velez
2025-05-18 5:48 ` Greg KH
2025-05-18 10:58 ` Jonathan Velez
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=2025051804-postage-tremble-d9d1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=jonvelez12345@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.