From: Akira Yokosawa <akiyks@gmail.com>
To: rdunlap@infradead.org
Cc: amd-gfx@lists.freedesktop.org, corbet@lwn.net,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: scripts/kernel-doc does not handle duplicate struct & function names (e.g., in amdgpu)
Date: Wed, 12 Jul 2023 12:32:10 +0900 [thread overview]
Message-ID: <0475d177-4c01-0988-0b34-3099dd703498@gmail.com> (raw)
In-Reply-To: <b5ebc891-ee63-1638-0377-7b512d34b823@infradead.org>
Hi Randy,
> [just documenting this for posterity or in case someone wants to fix it.]
>
> In drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c, one can find both
>
> struct amdgpu_vm_tlb_seq_cb {...};
>
> and
> static void amdgpu_vm_tlb_seq_cb(...)
>
> Of course C has no problem with this, but kernel-doc reports:
>
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:833: WARNING: Duplicate C declaration, also defined at gpu/amdgpu/driver-core:115.
>
> And of course, if the name of one of them is changed, kernel-doc is all happy...
> not that I am suggesting that one of them should be changed.
>
> I just want to make people aware of this. (or maybe people are already aware of this?)
The duplicate warning is emitted from Sphinx, not kernel-doc.
This is a bug of Sphinx >=3.1, first reported by Mauro back in September 2020 at:
https://github.com/sphinx-doc/sphinx/issues/8241
It was closed when a local fix was presented. Unfortunately, it was not
merged at the time and a subsequent pull request was opened at:
https://github.com/sphinx-doc/sphinx/pull/8313
It is not merged yet and carries a milestone of Sphinx 7.x.
Looks like we need to wait patiently.
Thanks, Akira
>
> --
> ~Randy
next prev parent reply other threads:[~2023-07-12 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 2:37 Randy Dunlap
2023-07-12 3:32 ` Akira Yokosawa [this message]
2023-07-12 3:45 ` Randy Dunlap
2023-07-12 5:42 ` Mauro Carvalho Chehab
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=0475d177-4c01-0988-0b34-3099dd703498@gmail.com \
--to=akiyks@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®