From: "André Almeida" <andrealmeid@collabora.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Eric Biggers <ebiggers@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Jens Axboe <axboe@kernel.dk>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Mike Rapoport <rppt@kernel.org>, Moritz Fischer <mdf@kernel.org>,
Puranjay Mohan <puranjay12@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Satya Tangirala <satyat@google.com>,
Takashi Iwai <tiwai@suse.com>, Tom Rix <trix@redhat.com>,
alsa-devel@alsa-project.org, linux-fpga@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v4 22/52] docs: get rid of :c:type explicit declarations for structs
Date: Wed, 30 Sep 2020 13:50:46 -0300 [thread overview]
Message-ID: <fd8bf973-3c22-a492-39e5-2164ce6724db@collabora.com> (raw)
In-Reply-To: <f74a2b4e1c8c475b5a053f5edd9da5a818be4b1f.1601467849.git.mchehab+huawei@kernel.org>
On 9/30/20 10:24 AM, Mauro Carvalho Chehab wrote:
> The :c:type:`foo` only works properly with structs before
> Sphinx 3.x.
>
> On Sphinx 3.x, structs should now be declared using the
> .. c:struct, and referenced via :c:struct tag.
>
> As we now have the automarkup.py macro, that automatically
> convert:
> struct foo
>
> into cross-references, let's get rid of that, solving
> several warnings when building docs with Sphinx 3.x.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
> Documentation/block/blk-mq.rst | 8 +++----
Regarding blk-mq.rst:
Reviewed-by: André Almeida <andrealmeid@collabora.com>
next prev parent reply other threads:[~2020-09-30 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1601467849.git.mchehab+huawei@kernel.org>
2020-09-30 13:24 ` [PATCH v4 22/52] docs: get rid of :c:type explicit declarations for structs Mauro Carvalho Chehab
2020-09-30 14:26 ` Mike Rapoport
2020-09-30 15:01 ` Takashi Iwai
2020-09-30 16:50 ` André Almeida [this message]
2020-09-30 13:25 ` [PATCH v4 40/52] docs: fpga: replace :c:member: macros Mauro Carvalho Chehab
2020-09-30 23:46 ` Moritz Fischer
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=fd8bf973-3c22-a492-39e5-2164ce6724db@collabora.com \
--to=andrealmeid@collabora.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alexandru.ardelean@analog.com \
--cc=alsa-devel@alsa-project.org \
--cc=anshuman.khandual@arm.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=grandmaster@al2klimov.de \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=mdf@kernel.org \
--cc=perex@perex.cz \
--cc=puranjay12@gmail.com \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=satyat@google.com \
--cc=tiwai@suse.com \
--cc=trix@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).