From: Jonathan Corbet <corbet@lwn.net>
To: Kevin Paul Reddy Janagari <kevinpaul468@gmail.com>,
rdunlap@infradead.org, rbrasga@uci.edu, kevinpaul468@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: skhan@linuxfoundation.org
Subject: Re: [PATCH] Added usb_string function to a namespace
Date: Mon, 14 Apr 2025 10:38:56 -0600 [thread overview]
Message-ID: <87ecxuaean.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250405165116.147958-1-kevinpaul468@gmail.com>
Kevin Paul Reddy Janagari <kevinpaul468@gmail.com> writes:
> with reference to WARNING:
> Duplicate C declaration, also defined at driver-api/usb/gadget:804
> There is a function usb_string in the file message.c,
> there is also a struct usb_string in the kernel api headers.
> The docs is unable to index the function as the index is occupied by struct
> This fix adds messgae.c to the usb_core namespace (in docs) hence providing
> usb_sting a unique index usb_core.usb_string()
>
> Signed-off-by: Kevin Paul Reddy Janagari <kevinpaul468@gmail.com>
> ---
> Documentation/driver-api/usb/usb.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/driver-api/usb/usb.rst b/Documentation/driver-api/usb/usb.rst
> index 89f9c37bb979..976fb4221062 100644
> --- a/Documentation/driver-api/usb/usb.rst
> +++ b/Documentation/driver-api/usb/usb.rst
> @@ -161,6 +161,7 @@ rely on 64bit DMA to eliminate another kind of bounce buffer.
> .. kernel-doc:: drivers/usb/core/urb.c
> :export:
>
> +.. c:namespace:: usb_core
> .. kernel-doc:: drivers/usb/core/message.c
> :export:
I hate this sort of workaround ... but so be it. Someday maybe it won't
be needed...
Applied, thanks,
jon
prev parent reply other threads:[~2025-04-14 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 16:51 [PATCH] Added usb_string function to a namespace Kevin Paul Reddy Janagari
2025-04-06 11:08 ` Akira Yokosawa
2025-04-14 16:38 ` Jonathan Corbet [this message]
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=87ecxuaean.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=kevinpaul468@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrasga@uci.edu \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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