From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linuxarm@huawei.com, mauro.chehab@huawei.com,
Bingbu Cao <bingbu.cao@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/9] media: docs: ipu3.rst: rely at automarkup extension
Date: Wed, 30 Sep 2020 12:19:34 +0300 [thread overview]
Message-ID: <20200930091934.GL26842@paasikivi.fi.intel.com> (raw)
In-Reply-To: <b9d4cdf89bafb131dab4030c3e8789f5e1c14193.1601447236.git.mchehab+huawei@kernel.org>
On Wed, Sep 30, 2020 at 08:35:56AM +0200, Mauro Carvalho Chehab wrote:
> There are several :c:type: definitions there, in order to
> do cross-references with the driver's documentation.
>
> Those are broken when docs are built with Sphinx 3.x, as
> it would require :c:struct: instead.
>
> For Sphinx < 3.x, the automarkup.py extension is able to do the
> replacement already, and a future improvement on it should make
> it also work with Sphinx 3.x.
>
> So, get rid of the usage of the :c:type: macro there.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Thanks!
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Sakari Ailus
next prev parent reply other threads:[~2020-09-30 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 6:35 [PATCH 0/9] Address several issues when building media docs with Sphinx 3.x Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 1/9] media: camera-sensor.rst: fix a doc build warning Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 2/9] media: glossary.rst: use the right case for glossary entries Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 3/9] media: docs: ipu3.rst: rely at automarkup extension Mauro Carvalho Chehab
2020-09-30 9:19 ` Sakari Ailus [this message]
2020-09-30 6:35 ` [PATCH 4/9] media: dvb-frontends: remove a clone of a kernel-doc markup at zd1301_demod.h Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 5/9] media: v4l2-subdev.rst: get rid of a duplicatd kernel-doc markup Mauro Carvalho Chehab
2020-09-30 6:35 ` [PATCH 6/9] media: cec-core.rst: fix warnings with Sphinx 3.0+ Mauro Carvalho Chehab
2020-09-30 6:36 ` [PATCH 7/9] media: v4l2-subdev.h: fix a kernel-doc markup Mauro Carvalho Chehab
2020-09-30 6:36 ` [PATCH 8/9] media: hist-v4l2.rst: remove struct duplication Mauro Carvalho Chehab
2020-09-30 6:36 ` [PATCH 9/9] media: hist-v4l2.rst: remove :c:`type` from structs and enums 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=20200930091934.GL26842@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mauro.chehab@huawei.com \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--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
all inboxes | Powered by JetHome®