All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Usman Akinyemi <usmanakinyemi202@gmail.com>
Cc: Thinh.Nguyen@synopsys.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: Fix documentation warning for sg member
Date: Thu, 23 Jan 2025 15:22:49 +0100	[thread overview]
Message-ID: <2025012322-fit-flagship-381c@gregkh> (raw)
In-Reply-To: <CAPSxiM9vF0=fzOovxC2nj1t1Naxx9T=QJPaN-oi5U-h7s5OwLQ@mail.gmail.com>

On Thu, Jan 23, 2025 at 07:47:18PM +0530, Usman Akinyemi wrote:
> On Thu, Jan 23, 2025 at 7:37 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Jan 23, 2025 at 01:31:02PM +0530, Usman Akinyemi wrote:
> > > The 'sg' member in struct dwc3_request was undocumented, causing a
> > > documentation warning when building the kernel docs.
> > >
> > > This patch adds a description for the 'sg' field, resolving the warning.
> > >
> > > Signed-off-by: Usman Akinyemi <usmanakinyemi202@gmail.com>
> >
> > What commit id does this fix?  And what about the reported-by: line?
> >
> > thanks,
> >
> Hi Greg,
> 
> Thanks for replying.
> 
> I was applying to Linux Mentorship(LFX) for fixing the Linux Kernel Bugs.
> One of the tasks was to look for documentation warnings and I saw this.
> 
> I created a patch for it and sent it also. So, it is not reported.

It was, you might have missed it on the mailing list:
	https://lore.kernel.org/r/20250120182219.30dcb3c6@canb.auug.org.au

Also it still needs a "Fixes:" tag.

thanks,

greg k-h

  reply	other threads:[~2025-01-23 14:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  8:01 [PATCH] usb: dwc3: Fix documentation warning for sg member Usman Akinyemi
2025-01-23 14:07 ` Greg KH
2025-01-23 14:17   ` Usman Akinyemi
2025-01-23 14:22     ` Greg KH [this message]
2025-01-23 15:15       ` Usman Akinyemi
2025-01-23 15:13 ` [PATCH v2] " Usman Akinyemi
2025-01-23 15:38   ` Greg KH
2025-01-23 15:52     ` Usman Akinyemi
2025-01-23 15:57       ` Greg KH
2025-01-23 16:11         ` Usman Akinyemi

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=2025012322-fit-flagship-381c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=usmanakinyemi202@gmail.com \
    /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.