From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
"André Almeida" <andrealmeid@collabora.com>,
"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>,
"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,
"Takashi Iwai" <tiwai@suse.de>,
"Mike Rapoport" <rppt@linux.ibm.com>
Subject: Re: [PATCH v5 22/52] docs: get rid of :c:type explicit declarations for structs
Date: Tue, 6 Oct 2020 18:41:52 +0200 [thread overview]
Message-ID: <20201006164152.GB36638@kroah.com> (raw)
In-Reply-To: <1f9d7dfd5e8557b55218af01045331939f1add28.1601992016.git.mchehab+huawei@kernel.org>
On Tue, Oct 06, 2020 at 04:03:19PM +0200, 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.
>
> Reviewed-by: André Almeida <andrealmeid@collabora.com> # blk-mq.rst
> Reviewed-by: Takashi Iwai <tiwai@suse.de> # sound
> Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2020-10-06 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1601992016.git.mchehab+huawei@kernel.org>
2020-10-06 14:03 ` [PATCH v5 22/52] docs: get rid of :c:type explicit declarations for structs Mauro Carvalho Chehab
2020-10-06 16:41 ` Greg Kroah-Hartman [this message]
2020-10-06 14:03 ` [PATCH v5 40/52] docs: fpga: replace :c:member: macros 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=20201006164152.GB36638@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alexandru.ardelean@analog.com \
--cc=alsa-devel@alsa-project.org \
--cc=andrealmeid@collabora.com \
--cc=anshuman.khandual@arm.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=ebiggers@kernel.org \
--cc=grandmaster@al2klimov.de \
--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=rppt@linux.ibm.com \
--cc=satyat@google.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--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).