public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: sfr@canb.auug.org.au
Cc: bhelgaas@google.com, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, mchehab+samsung@kernel.org,
	Akira Yokosawa <akiyks@gmail.com>,
	linux-doc@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the origin tree
Date: Wed, 22 Jan 2025 19:00:43 +0900	[thread overview]
Message-ID: <07507296-a37b-4543-97cb-0560ef7fb7b8@gmail.com> (raw)
In-Reply-To: <20250122170335.148a23b0@canb.auug.org.au>

[+CC: linux-doc]

Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next build (htmldocs) produced this warning:
> 
> Documentation/power/video.rst:213: WARNING: Footnote [#] is not referenced. [ref.footnote]
> 
> This warning has presumably been there for a long time.
> 
> I don't know what causes it - maybe it needs a space before the opening
> bracket?

Stephen, fhve you upgraded your Sphinx recently?

In "Bugs Fixed" section of Sphinx 8.1.0 changelog [1], there is an item which
reads:

    - #12730: The UnreferencedFootnotesDetector transform has been improved
      to more consistently detect unreferenced footnotes. Note, the priority
      of the transform has been changed from 200 to 622, so that it now runs
      after the docutils Footnotes resolution transform. Patch by Chris Sewell.

So the above warning is real and prior versions of Sphinx just can't flag it.

To silence it, you need to get rid of the unreferenced footnote, I guess.

[1]: https://www.sphinx-doc.org/en/master/changes/8.1.html#id3

        HTH, Akira

> 
> Introduced by commit
> 
>   151f4e2bdc7a ("docs: power: convert docs to ReST and rename to *.rst")
> 
> from v5.3-rc1
> 
> I am just going over left over warnings in he documentation.
> 
> -- 
> Cheers,
> Stephen Rothwell


  reply	other threads:[~2025-01-22 10:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22  6:03 linux-next: build warning after merge of the origin tree Stephen Rothwell
2025-01-22 10:00 ` Akira Yokosawa [this message]
2025-01-22 13:39   ` Bagas Sanjaya
2025-01-22 14:46     ` Akira Yokosawa
2025-01-23  0:27       ` Bagas Sanjaya
2025-01-22 21:57   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-03-25  1:17 Stephen Rothwell
2022-01-17  0:45 Stephen Rothwell
2022-01-17  1:27 ` Suren Baghdasaryan
2022-01-17  2:24   ` Stephen Rothwell
2022-01-17 22:01     ` Andrew Morton
2021-01-06 22:05 Stephen Rothwell
2021-01-06 22:23 ` Johannes Berg
2021-01-06 22:44   ` Stephen Rothwell
2021-01-06 22:46     ` Johannes Berg
2021-01-06 23:20       ` Stephen Rothwell
2019-11-27 20:59 Stephen Rothwell
2019-11-28  8:11 ` Linus Walleij
2012-05-14  0:44 Stephen Rothwell
2012-05-14  3:00 ` David Miller

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=07507296-a37b-4543-97cb-0560ef7fb7b8@gmail.com \
    --to=akiyks@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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