From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Corentin Labbe" <clabbe.montjoie@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Maxime Ripard" <mripard@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: [PATCH 0/2] Fix new warnings at linux-next
Date: Fri, 9 Oct 2020 14:15:29 +0200 [thread overview]
Message-ID: <cover.1602245659.git.mchehab+huawei@kernel.org> (raw)
There are some file renames at linux-next that are causing some
new documentation warnings. Address them.
Mauro Carvalho Chehab (2):
MAINTAINERS: fix broken doc refs due to yaml conversion
crypto: sun8x-ce*: update entries to its documentation
Documentation/devicetree/bindings/clock/hi6220-clock.txt | 2 +-
MAINTAINERS | 9 ++++-----
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-hash.c | 2 +-
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-prng.c | 2 +-
drivers/crypto/allwinner/sun8i-ce/sun8i-ce-trng.c | 2 +-
.../devicetree/bindings/net/wireless/silabs,wfx.yaml | 2 +-
6 files changed, 9 insertions(+), 10 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-09 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 12:15 Mauro Carvalho Chehab [this message]
2020-10-09 12:15 ` [PATCH 1/2] MAINTAINERS: fix broken doc refs due to yaml conversion Mauro Carvalho Chehab
2020-10-12 19:21 ` Rob Herring
2020-10-13 8:52 ` Mauro Carvalho Chehab
2020-10-21 10:00 ` Mauro Carvalho Chehab
2020-10-12 19:26 ` Stephen Boyd
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=cover.1602245659.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=clabbe.montjoie@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jerome.pouiller@silabs.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=wens@csie.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).