The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 14:11:08 +0200	[thread overview]
Message-ID: <2025051805-astound-unaligned-db5c@gregkh> (raw)
In-Reply-To: <C49E4FFB-81F5-40DF-8DD6-5BB4A3B782B7@gmail.com>

On Sun, May 18, 2025 at 08:08:46AM -0400, Jonathan Velez wrote:
> 
> 
> > On May 18, 2025, at 7:58 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > 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
> > 
> > What commit id does this fix?
>    I pulled the mainline and worked on the “for-next” branch. Is that the correct process? Should I be using the “master” branch instead?
> > 
> > And are you sure you made this against the right tree?  I do not see
> > "sg" as a member of this stucture at all anymore.
>    This was the last commit on the “for-next” branch:
> 
>    commit ffd294d346d185b70e28b1a28abe367bbfe53c04 

That is the 6.13 release from way back on January 19.  I think a few
other things have happened since then :)

Please work against either the development branch of the subsystem you
are submitting changes for, OR against the linux-next tree which merges
all subsystems together, so that you do not accidentally use an old
tree.

thanks,

greg k-h

  reply	other threads:[~2025-05-18 12:12 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
2025-05-18 11:58 ` Greg KH
2025-05-18 12:08   ` Jonathan Velez
2025-05-18 12:11     ` Greg KH [this message]
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=2025051805-astound-unaligned-db5c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox