From: Jonathan Corbet <corbet@lwn•net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
Cc: kvm@vger•kernel.org,
Linux Doc Mailing List <linux-doc@vger•kernel.org>,
linux-pci@vger•kernel.org,
Linus Walleij <linus.walleij@linaro•org>,
dri-devel@lists•freedesktop.org, linux-unionfs@vger•kernel.org,
linux-mm@kvack•org, netdev@vger•kernel.org,
linux-i2c@vger•kernel.org, linux1394-devel@lists•sourceforge.net,
kvmarm@lists•cs.columbia.edu, linux-arch@vger•kernel.org,
Rob Herring <robh@kernel•org>,
Geert Uytterhoeven <geert+renesas@glider•be>,
linux-rdma@vger•kernel.org,
Kishon Vijay Abraham I <kishon@ti•com>,
linux-rockchip@lists•infradead.org,
Matthias Kaehlcke <mka@chromium•org>,
Sandeep Maheswaram <sanm@codeaurora•org>,
linux-media@vger•kernel.org, devicetree@vger•kernel.org,
linux-afs@lists•infradead.org, linux-arm-msm@vger•kernel.org,
ecryptfs@vger•kernel.org, kvm-ppc@vger•kernel.org,
Stephen Boyd <swboyd@chromium•org>,
Maxime Ripard <maxime@cerno•tech>,
linux-arm-kernel@lists•infradead.org, linux-edac@vger•kernel.org,
Matthias Brugger <mbrugger@suse•com>,
Yuti Amonkar <yamonkar@cadence•com>,
linux-ide@vger•kernel.org, linux-ntfs-dev@lists•sourceforge.net,
freedreno@lists•freedesktop.org, linux-usb@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-spi@vger•kernel.org,
linux-crypto@vger•kernel.org, Sudeep Holla <sudeep.holla@arm•com>,
linux-fsdevel@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
ocfs2-devel@oss•oracle.com
Subject: Re: [PATCH v2 00/33] Documentation fixes for Kernel 5.8
Date: Mon, 20 Apr 2020 15:43:16 -0600 [thread overview]
Message-ID: <20200420154316.28e42905@lwn.net> (raw)
In-Reply-To: <cover.1586881715.git.mchehab+huawei@kernel.org>
On Tue, 14 Apr 2020 18:48:26 +0200
Mauro Carvalho Chehab <mchehab+huawei@kernel•org> wrote:
> Patches 1 to 5 contain changes to the documentation toolset:
>
> - The first 3 patches help to reduce a lot the number of reported
> kernel-doc issues, by making the tool more smart.
>
> - Patches 4 and 5 are meant to partially address the PDF
> build, with now requires Sphinx version 2.4 or upper.
>
> The remaining patches fix broken references detected by
> this tool:
>
> ./scripts/documentation-file-ref-check
>
> and address other random errors due to tags being mis-interpreted
> or mis-used.
>
> They are independent each other, but some may depend on
> the kernel-doc improvements.
>
> PS.: Due to the large number of C/C, I opted to keep a smaller
> set of C/C at this first e-mail (only e-mails with "L:" tag from
> MAINTAINERS file).
OK, I've applied this set, minus #17 which was applied elsewhere.
Thanks,
jon
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-20 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 16:48 [PATCH v2 00/33] Documentation fixes for Kernel 5.8 Mauro Carvalho Chehab
2020-04-14 16:48 ` [PATCH v2 10/33] docs: fix broken references for ReST files that moved around Mauro Carvalho Chehab
2020-04-16 8:31 ` Corentin Labbe
2020-04-14 16:48 ` [PATCH v2 12/33] docs: amu: supress some Sphinx warnings Mauro Carvalho Chehab
2020-04-14 16:48 ` [PATCH v2 13/33] docs: arm64: booting.rst: get rid of some warnings Mauro Carvalho Chehab
2020-04-14 16:48 ` [PATCH v2 28/33] docs: dt: rockchip, dwc3.txt: fix a pointer to a renamed file Mauro Carvalho Chehab
2020-04-14 21:02 ` Rob Herring
2020-04-20 21:43 ` Jonathan Corbet [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=20200420154316.28e42905@lwn.net \
--to=corbet@lwn$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=ecryptfs@vger$(echo .)kernel.org \
--cc=freedreno@lists$(echo .)freedesktop.org \
--cc=geert+renesas@glider$(echo .)be \
--cc=kishon@ti$(echo .)com \
--cc=kvm-ppc@vger$(echo .)kernel.org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=kvmarm@lists$(echo .)cs.columbia.edu \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-afs@lists$(echo .)infradead.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-i2c@vger$(echo .)kernel.org \
--cc=linux-ide@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-media@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-ntfs-dev@lists$(echo .)sourceforge.net \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-rockchip@lists$(echo .)infradead.org \
--cc=linux-spi@vger$(echo .)kernel.org \
--cc=linux-unionfs@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=linux1394-devel@lists$(echo .)sourceforge.net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maxime@cerno$(echo .)tech \
--cc=mbrugger@suse$(echo .)com \
--cc=mchehab+huawei@kernel$(echo .)org \
--cc=mka@chromium$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ocfs2-devel@oss$(echo .)oracle.com \
--cc=robh@kernel$(echo .)org \
--cc=sanm@codeaurora$(echo .)org \
--cc=sudeep.holla@arm$(echo .)com \
--cc=swboyd@chromium$(echo .)org \
--cc=yamonkar@cadence$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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