From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Marek Behún" <kabel@kernel.org>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc tree
Date: Tue, 30 Jul 2024 20:05:07 +1000 [thread overview]
Message-ID: <20240730200507.1ce43e56@canb.auug.org.au> (raw)
In-Reply-To: <20240702135532.18156015@dellmb>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Hi Marek,
On Tue, 2 Jul 2024 13:55:32 +0200 Marek Behún <kabel@kernel.org> wrote:
>
> On Tue, 2 Jul 2024 17:49:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the arm-soc tree, today's linux-next build (htmldocs)
> > produced this warning:
> >
> > Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu:26: ERROR: Unexpected indentation.
> > Documentation/ABI/testing/sysfs-bus-i2c-devices-turris-omnia-mcu:26: WARNING: Block quote ends without a blank line; unexpected unindent.
> >
> > Introduced by commit
> >
> > dfa556e45ae9 ("platform: cznic: turris-omnia-mcu: Add support for MCU connected GPIOs")
I am still seeing these warnings.
> I don't see what can be the problem on those lines. Is it possible to
> build that specific file?
I don't know, sorry.
The warnings are probably caused by the line beginning with " change
the LEDs panel" or the earlier line starting with '-'.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-30 10:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 7:49 linux-next: build warning after merge of the arm-soc tree Stephen Rothwell
2024-07-02 11:55 ` Marek Behún
2024-07-30 10:05 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-22 0:48 Stephen Rothwell
2023-06-22 8:19 ` Arnd Bergmann
2023-06-22 8:26 ` Krzysztof Kozlowski
2023-06-22 13:55 ` Rob Herring
2021-12-22 21:59 Stephen Rothwell
2021-12-22 23:22 ` Arnd Bergmann
2021-12-22 23:58 ` Florian Fainelli
2021-12-23 8:50 ` Arınç ÜNAL
2021-12-23 18:18 ` Florian Fainelli
2021-10-25 23:39 Stephen Rothwell
2021-10-26 6:15 ` Joel Stanley
2022-01-20 3:22 ` Stephen Rothwell
2022-01-20 6:03 ` ChiaWei Wang
2021-04-06 0:45 Stephen Rothwell
2021-04-06 6:34 ` Krzysztof Kozlowski
2019-08-15 23:25 Stephen Rothwell
2019-08-15 23:23 Stephen Rothwell
2019-04-29 23:28 Stephen Rothwell
2019-05-03 6:49 ` Linus Walleij
2019-05-03 12:57 ` Arnd Bergmann
2014-01-19 23:39 Stephen Rothwell
2012-03-19 7:39 Stephen Rothwell
2012-03-19 9:40 ` Arnd Bergmann
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=20240730200507.1ce43e56@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
/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