From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: gpu: nouveau.rst: fix a wrong path
Date: Wed, 30 Jul 2025 12:17:13 -0700 [thread overview]
Message-ID: <c0416cd1-0055-4ca9-9780-e885ead4939b@infradead.org> (raw)
In-Reply-To: <20250730102010.2976882-1-mchehab+huawei@kernel.org>
On 7/30/25 3:20 AM, Mauro Carvalho Chehab wrote:
> The nouveau.rst file is pointing to a file at the wrong path,
> causing doctree cache expires and forcing kernel-doc to run every
> time.
>
> Fix it.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Hi Mauro,
Bagas sent a patch for this on June 10 and it's already fixed in linux-next.
It's probably sitting in a DRM tree waiting for a PR.
Thanks.
> ---
> Documentation/gpu/nouveau.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/gpu/nouveau.rst b/Documentation/gpu/nouveau.rst
> index b8c801e0068c..cab2e81013bc 100644
> --- a/Documentation/gpu/nouveau.rst
> +++ b/Documentation/gpu/nouveau.rst
> @@ -25,7 +25,7 @@ providing a consistent API to upper layers of the driver stack.
> GSP Support
> ------------------------
>
> -.. kernel-doc:: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c
> +.. kernel-doc:: drivers/gpu/drm/nouveau/nvkm/subdev/gsp/rm/r535/rpc.c
> :doc: GSP message queue element
>
> .. kernel-doc:: drivers/gpu/drm/nouveau/include/nvkm/subdev/gsp.h
--
~Randy
prev parent reply other threads:[~2025-07-30 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:20 [PATCH] docs: gpu: nouveau.rst: fix a wrong path Mauro Carvalho Chehab
2025-07-30 19:17 ` 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=c0416cd1-0055-4ca9-9780-e885ead4939b@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.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;
as well as URLs for NNTP newsgroup(s).