From: Matthew Wilcox <willy@infradead.org>
To: Adam Turner <aaturnerpython@outlook.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Sphinx pre v3 -- removing support
Date: Fri, 3 Jun 2022 16:38:57 +0100 [thread overview]
Message-ID: <YporEWa2eV2Rvj3X@casper.infradead.org> (raw)
In-Reply-To: <LO3P123MB26812980BECD5299A27BA163C2A19@LO3P123MB2681.GBRP123.PROD.OUTLOOK.COM>
On Fri, Jun 03, 2022 at 03:30:29PM +0000, Adam Turner wrote:
> > There's a bug I've been meaning to track down & report where _some_ links
> > are broken when building with the Sphinx natively installed on my system
> > (Debian 4.3.2-1). I haven't bothered because (a) life is short and (b)
> > it's not affecting the kernel.org build. If we're going to ask
> > kernel.org to move to a newer version of Sphinx, we should make sure
> > that the links won't be broken on whatever version we pick.
>
> > An example:
> > <span class="kt"><span class="pre">void</span></span><span class="w"> </span><span class="p"><span class="pre">*</span></span><span class="sig-name descname"><span class="n"><span class="pre">kmap_local_folio</span></span></span><span class="sig-paren">(</span><span class="k"><span class="pre">struct</span></span><span class="w"> </span><a class="reference internal" href="#c.kmap_local_folio" title="folio"><span class="n"><span class="pre">folio</span></span></a><span class="w"> </span><span class="p"><span class="pre">*</span></span><span class="n"><span class="pre">folio</span></span>, <span class="n"><span class="pre">size_t</span></span><span class="w"> </span><span class="n"><span class="pre">offset</span></span><span class="sig-paren">)</span><a class="headerlink" href="#c.kmap_local_folio" title="Permalink to this definition">¶</a><br /></dt>
>
> > Other than that being a big pile of html, that <a href> around 'folio'
> > should be a link to struct folio and not back to the c.kmap_local_folio
> > anchor.
>
> > I appreciate this is not a great bug report, but I find the entire
> > build system beyond my comprehension.
>
> Do you have the reST source behind this rendered HTML? I can then try
> and find a minimal reproducer and see if we can fix within Sphinx.
Alas, I don't. I don't even know if this is a Sphinx bug or if it's a
bug in one of the kernel addons. It's generated by scripts/kernel-doc
from:
/**
* kmap_local_folio - Map a page in this folio for temporary usage
* @folio: The folio containing the page.
* @offset: The byte offset within the folio which identifies the page.
*
...
*/
static inline void *kmap_local_folio(struct folio *folio, size_t offset);
I see an intermediate file in
Documentation/output/_sources/vm/highmem.rst.txt
but that doesn't include the output from scripts/kernel-doc.
This is why I've been reluctant to report it; I lack enough
understanding to be useful :-(
next prev parent reply other threads:[~2022-06-03 15:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 14:13 Sphinx pre v3 -- removing support Adam Turner
2022-06-03 14:21 ` Jonathan Corbet
2022-06-03 14:30 ` Adam Turner
2022-06-03 21:34 ` Jonathan Corbet
2022-06-03 15:22 ` Matthew Wilcox
2022-06-03 15:30 ` Adam Turner
2022-06-03 15:38 ` Matthew Wilcox [this message]
2022-06-03 15:42 ` Konstantin Ryabitsev
2022-06-03 16:00 ` Jonathan Corbet
2022-06-03 16:26 ` Konstantin Ryabitsev
2022-06-03 21:50 ` Jonathan Corbet
2022-06-13 15:40 ` Konstantin Ryabitsev
2022-06-13 16:00 ` Matthew Wilcox
2022-06-13 16:16 ` Adam Turner
2022-06-13 16:19 ` Matthew Wilcox
2022-06-03 22:11 ` Jonathan Corbet
2022-06-03 15:05 ` Akira Yokosawa
2022-06-03 15:27 ` Adam Turner
2022-06-03 15:44 ` Jani Nikula
2022-06-03 15:54 ` Adam Turner
2022-06-03 16:36 ` Akira Yokosawa
2022-06-03 19:05 ` Jani Nikula
2022-06-04 8:13 ` Mauro Carvalho Chehab
2022-07-02 11:23 ` 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=YporEWa2eV2Rvj3X@casper.infradead.org \
--to=willy@infradead.org \
--cc=aaturnerpython@outlook.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.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).