From: Randy Dunlap <rdunlap@infradead.org>
To: HyeonSu Jeon <dev.hyeonsu.jeon@gmail.com>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch, corbet@lwn.net
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: nouveau: remove invalid kernel-doc reference to r535.c
Date: Sun, 15 Jun 2025 20:04:56 -0700 [thread overview]
Message-ID: <217e3774-8a28-4adc-b2df-a31b6ba5a382@infradead.org> (raw)
In-Reply-To: <20250616021742.8304-1-dev.hyeonsu.jeon@gmail.com>
Hi,
On 6/15/25 7:17 PM, HyeonSu Jeon wrote:
> The file drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c does not exist
> in the tree, but is referenced in gsp.rst via a kernel-doc directive.
> This causes an error during the documentation build
>
> Removing this refernce resolves the error
>
> Signed-off-by: HyeonSu Jeon <dev.hyeonsu.jeon@gmail.com>
Thanks for your patch.
A previous patch has already been applied to drm-misc-fixes:
https://lore.kernel.org/linux-doc/20250611020805.22418-2-bagasdotme@gmail.com/
> ---
> Documentation/gpu/nouveau.rst | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/Documentation/gpu/nouveau.rst b/Documentation/gpu/nouveau.rst
> index b8c801e0068c..cab4a8eda850 100644
> --- a/Documentation/gpu/nouveau.rst
> +++ b/Documentation/gpu/nouveau.rst
> @@ -25,8 +25,5 @@ providing a consistent API to upper layers of the driver stack.
> GSP Support
> ------------------------
>
> -.. kernel-doc:: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c
> - :doc: GSP message queue element
> -
> .. kernel-doc:: drivers/gpu/drm/nouveau/include/nvkm/subdev/gsp.h
> :doc: GSP message handling policy
--
~Randy
prev parent reply other threads:[~2025-06-16 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 2:17 [PATCH] docs: nouveau: remove invalid kernel-doc reference to r535.c HyeonSu Jeon
2025-06-16 3:04 ` Randy Dunlap [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=217e3774-8a28-4adc-b2df-a31b6ba5a382@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dev.hyeonsu.jeon@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
/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;
as well as URLs for NNTP newsgroup(s).