From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the usb.current tree
Date: Thu, 1 Sep 2022 07:50:47 +1000 [thread overview]
Message-ID: <20220901075048.7b281231@canb.auug.org.au> (raw)
In-Reply-To: <Yw9vYaqczVlWzONt@rowland.harvard.edu>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi Alan,
On Wed, 31 Aug 2022 10:25:37 -0400 Alan Stern <stern@rowland.harvard.edu> wrote:
>
> On Wed, Aug 31, 2022 at 03:24:58PM +1000, Stephen Rothwell wrote:
> >
> > After merging the usb.current tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/driver-api/usb/usb:176: /home/sfr/next/next/drivers/usb/core/hub.c:6040: WARNING: Unknown target name: "pre".
> >
> > Introduced by commit
> >
> > 9c6d778800b9 ("USB: core: Prevent nested device-reset calls")
>
> I don't fully understand this bug report. Would it be fixed by changing
> "pre_" to "pre_reset()" in the kerneldoc?
I would presume so.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-31 21:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 5:24 linux-next: build warning after merge of the usb.current tree Stephen Rothwell
2022-08-31 14:25 ` Alan Stern
2022-08-31 21:50 ` Stephen Rothwell [this message]
2022-09-01 14:36 ` [PATCH] USB: core: Fix RST error in hub.c Alan Stern
2022-09-05 3:13 ` Bagas Sanjaya
-- strict thread matches above, loose matches on Subject: below --
2012-01-25 0:20 linux-next: build warning after merge of the usb.current tree Stephen Rothwell
2012-01-25 0:33 ` Greg KH
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=20220901075048.7b281231@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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