linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, "Jonathan Corbet" <corbet@lwn.net>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Alexandre Courbot" <acourbot@chromium.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Ezequiel Garcia" <ezequiel@collabora.com>,
	"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
	"Helen Koike" <helen.koike@collabora.com>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Jernej Skrabec" <jernej.skrabec@siol.net>,
	"Jian-Jia Su" <jjsu@chromium.org>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Michael Tretter" <m.tretter@pengutronix.de>,
	"Paul Kocialkowski" <paul.kocialkowski@bootlin.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	"Ricardo Ribalda" <ribalda@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Sean Young" <sean@mess.org>,
	"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
	"Tomasz Figa" <tfiga@chromium.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 0/8] Improve support for building docs with Sphinx 3.1+
Date: Fri, 25 Sep 2020 09:31:58 +0200	[thread overview]
Message-ID: <20200925093158.2b605cc4@coco.lan> (raw)
In-Reply-To: <cover.1601014299.git.mchehab+huawei@kernel.org>

Em Fri, 25 Sep 2020 08:30:38 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:

> Sphinx 3.x new c domain code broke the doc build on several ways:
> 
> - it broke the cdomains.py extension that were giving namespace
>   support for C references;
> - it broke the automarkup script;
> - it broke c:type references that kernel-doc and other parts of the
>   kernel were using to do cross-references with C declarations.
> 
> This series address only part of those issues. It halves the number
> of warnings produced when Spinx 3.x is used.  Yet, we still
> have 1.7 K warnings.

At least some of the warnings seem to be due to some issues at
Sphinx 3.x. I opened an issue to Sphinx upstream:

	https://github.com/sphinx-doc/sphinx/issues/8241

Thanks,
Mauro

      parent reply	other threads:[~2020-09-25  7:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-25  6:30 [PATCH v3 0/8] Improve support for building docs with Sphinx 3.1+ Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 1/8] docs: cdomain.py: add support for a new Sphinx 3.1+ tag Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 2/8] docs: conf.py: disable automarkup for Sphinx 3.x Mauro Carvalho Chehab
2020-09-25 12:12   ` [PATCH v3.1 " Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 3/8] scripts: kernel-doc: make it more compatible with " Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 4/8] media: docs: make CEC documents compatible with Sphinx 3.1+ Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 7/8] media: docs: make MC documents more " Mauro Carvalho Chehab
2020-09-25  6:30 ` [PATCH v3 8/8] media: docs: make RC " Mauro Carvalho Chehab
2020-09-25  7:31 ` Mauro Carvalho Chehab [this message]

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=20200925093158.2b605cc4@coco.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=acourbot@chromium.org \
    --cc=arnd@arndb.de \
    --cc=boris.brezillon@collabora.com \
    --cc=corbet@lwn.net \
    --cc=ezequiel@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=jernej.skrabec@siol.net \
    --cc=jjsu@chromium.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.tretter@pengutronix.de \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=rdunlap@infradead.org \
    --cc=ribalda@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tfiga@chromium.org \
    /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).