From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: 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>,
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>,
Rajmohan Mani <rajmohan.mani@intel.com>
Subject: Re: [PATCH 1/3] media: ipu3.rst: Prune unreferenced footnotes
Date: Thu, 23 Jan 2025 07:27:45 +0000 [thread overview]
Message-ID: <Z5HvcW2WXibhsTgm@kekkonen.localdomain> (raw)
In-Reply-To: <20250122143456.68867-2-bagasdotme@gmail.com>
Hi Bagas,
Thanks for the patches.
On Wed, Jan 22, 2025 at 09:34:54PM +0700, Bagas Sanjaya wrote:
> Sphinx reports unreferenced footnotes warning on ipu3 docs:
>
> Documentation/admin-guide/media/ipu3.rst:592: WARNING: Footnote [#] is not referenced. [ref.footnote]
> Documentation/admin-guide/media/ipu3.rst:598: WARNING: Footnote [#] is not referenced. [ref.footnote]
>
> Fix above warnings by pruning unreferenced footnote to intel_ipu3.h
> UAPI header (already referenced in its full path in "Running mode and
> firmware binary selection") and by directly link to v4l-utils repo in
> ov5670 configuration example with media-ctl (since the example is in
> literal code block).
>
> Footnote numbers are unchanged.
>
> Cc: Rajmohan Mani <rajmohan.mani@intel.com>
> Fixes: dc794d3d2424 ("media: staging: ipu3-imgu: Move the UAPI header from include under include/uapi")
> Fixes: 34fc0e1bf892 ("media: doc-rst: Add Intel IPU3 documentation")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
The issues fixed by this patch have already been fixed in commit
688c0a6907a7c6e6776f314195c10536f249b37f (in media tree).
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2025-01-23 7:27 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 [this message]
2025-01-22 14:34 ` [PATCH 2/3] Documentation: ublk: Drop Stefan Hajnoczi's message footnote Bagas Sanjaya
2025-01-22 15:36 ` 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=Z5HvcW2WXibhsTgm@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--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=rajmohan.mani@intel.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