linux-kernel - Re: [PATCH] docs: usb: dwc3: add documentation of 'sg' field in dwc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025051805-astound-unaligned-db5c@gregkh>
Date: Sun, 18 May 2025 14:11:08 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Jonathan Velez <jonvelez12345@...il.com>
Cc: Thinh.Nguyen@...opsys.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: usb: dwc3: add documentation of 'sg' field in
 dwc3_request struct

On Sun, May 18, 2025 at 08:08:46AM -0400, Jonathan Velez wrote:
> 
> 
> > On May 18, 2025, at 7:58 AM, Greg KH <gregkh@...uxfoundation.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@...il.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