From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>,
Martin Jerabek <martin.jerabek01@gmail.com>,
Ondrej Ille <ondrej.ille@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] docs: ctucanfd: Use 'kernel-figure' directive instead of 'figure'
Date: Wed, 11 May 2022 13:37:31 +0700 [thread overview]
Message-ID: <YntZqxuLSci6f8Z+@debian.me> (raw)
In-Reply-To: <05d491d4-c498-9bab-7085-9c892b636d68@gmail.com>
On Tue, May 10, 2022 at 06:34:37PM +0900, Akira Yokosawa wrote:
> Two issues were observed in the ReST doc added by commit c3a0addefbde
> ("docs: ctucanfd: CTU CAN FD open-source IP core documentation.").
>
> The plain "figure" directive broke "make pdfdocs" due to a missing
> PDF figure. For conversion of SVG -> PDF to work, the "kernel-figure"
> directive, which is an extension for kernel documentations, should
> be used instead.
>
Does plain "figure" directive not currently support SVG file argument?
Because when I see reST documentation ([1]), it doesn't explicitly
mentioned supported image formats.
[1]: https://docutils.sourceforge.io/docs/ref/rst/directives.html#figure
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-05-11 6:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:34 [PATCH net-next] docs: ctucanfd: Use 'kernel-figure' directive instead of 'figure' Akira Yokosawa
2022-05-10 16:25 ` Pavel Pisa
2022-05-10 23:34 ` Akira Yokosawa
2022-05-11 7:23 ` Pavel Pisa
2022-05-10 23:45 ` [PATCH net-next v2] " Akira Yokosawa
2022-05-16 11:24 ` Akira Yokosawa
2022-05-16 19:31 ` Pavel Pisa
2022-05-11 6:37 ` Bagas Sanjaya [this message]
2022-05-11 10:52 ` [PATCH net-next] " Akira Yokosawa
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=YntZqxuLSci6f8Z+@debian.me \
--to=bagasdotme@gmail.com \
--cc=akiyks@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.jerabek01@gmail.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--cc=pisa@cmp.felk.cvut.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.