From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>, Networking <netdev@vger.kernel.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
Jakub Kicinski <kuba@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the net tree
Date: Mon, 11 Apr 2022 14:36:02 +1000 [thread overview]
Message-ID: <20220411143602.24aa559b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi all,
After merging the net tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/driver-api/infrastructure:35: drivers/base/dd.c:280: WARNING: Unexpected indentation.
Documentation/driver-api/infrastructure:35: drivers/base/dd.c:281: WARNING: Block quote ends without a blank line; unexpected unindent.
Introduced by commit
c8c43cee29f6 ("driver core: Fix driver_deferred_probe_check_state() logic")
Exposed by commit
74befa447e68 ("net: mdio: don't defer probe forever if PHY IRQ provider is missing")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-11 4:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 4:36 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-04 3:48 linux-next: build warnings after merge of the net tree Stephen Rothwell
2016-05-20 3:33 Stephen Rothwell
2016-05-20 5:57 ` David Miller
2011-08-12 1:53 Stephen Rothwell
2011-08-12 10:01 ` David Miller
2010-08-31 1:55 Stephen Rothwell
2010-08-31 4:56 ` David Miller
2010-09-01 1:25 ` Stephen Rothwell
2010-09-01 3:57 ` David Miller
2010-06-16 3:38 Stephen Rothwell
2010-06-16 4:52 ` David Miller
2010-06-16 6:30 ` Stephen Rothwell
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=20220411143602.24aa559b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vladimir.oltean@nxp.com \
/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