From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Media <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Block Devices <linux-block@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Power Management <linux-pm@vger.kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 2/3] Documentation: ublk: Drop Stefan Hajnoczi's message footnote
Date: Wed, 22 Jan 2025 21:34:55 +0700 [thread overview]
Message-ID: <20250122143456.68867-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20250122143456.68867-1-bagasdotme@gmail.com>
Sphinx reports unreferenced footnote warning pointing to ubd-control
message by Stefan Hajnoczi [1]:
Documentation/block/ublk.rst:336: WARNING: Footnote [#] is not referenced. [ref.footnote]
Drop the footnote to squash above warning.
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Fixes: 7a3d2225f1ae ("Documentation: document ublk")
Link: https://lore.kernel.org/linux-block/YoOr6jBfgVm8GvWg@stefanha-x1.localdomain/ [1]
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
Documentation/block/ublk.rst | 2 --
1 file changed, 2 deletions(-)
diff --git a/Documentation/block/ublk.rst b/Documentation/block/ublk.rst
index 51665a3e6a50cd..1e0e7358e14a96 100644
--- a/Documentation/block/ublk.rst
+++ b/Documentation/block/ublk.rst
@@ -333,6 +333,4 @@ References
.. [#userspace_readme] https://github.com/ming1/ubdsrv/blob/master/README
-.. [#stefan] https://lore.kernel.org/linux-block/YoOr6jBfgVm8GvWg@stefanha-x1.localdomain/
-
.. [#xiaoguang] https://lore.kernel.org/linux-block/YoOr6jBfgVm8GvWg@stefanha-x1.localdomain/
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-01-22 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 14:34 [PATCH 0/3] Tree-wide nreferenced footnotes fixes Bagas Sanjaya
2025-01-22 14:34 ` [PATCH 1/3] media: ipu3.rst: Prune unreferenced footnotes Bagas Sanjaya
2025-01-23 3:55 ` Cao, Bingbu
2025-01-23 7:27 ` Sakari Ailus
2025-01-22 14:34 ` Bagas Sanjaya [this message]
2025-01-22 15:36 ` [PATCH 2/3] Documentation: ublk: Drop Stefan Hajnoczi's message footnote Stefan Hajnoczi
2025-01-22 14:34 ` [PATCH 3/3] docs: power: Fix footnote reference for Toshiba Satellite P10-554 Bagas Sanjaya
2025-01-22 17:26 ` [PATCH 0/3] Tree-wide nreferenced footnotes fixes Jonathan Corbet
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=20250122143456.68867-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=axboe@kernel.dk \
--cc=bingbu.cao@intel.com \
--cc=corbet@lwn.net \
--cc=len.brown@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ming.lei@redhat.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stefanha@redhat.com \
--cc=tian.shu.qiu@intel.com \
/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