From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Benson Leung <bleung@google.com>,
Guenter Roeck <groeck@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the chrome-platform tree
Date: Mon, 16 May 2022 21:38:32 +1000 [thread overview]
Message-ID: <20220516213832.19127535@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi all,
After merging the chrome-platform tree, today's linux-next build
(htmldocs) produced this warning:
Documentation/ABI/testing/sysfs-driver-chromeos-acpi:2: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-driver-chromeos-acpi:11: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-driver-chromeos-acpi:22: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-driver-chromeos-acpi:56: WARNING: Unexpected indentation.
Introduced by commit
0a4cad9c11ad ("platform/chrome: Add ChromeOS ACPI device driver")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-05-16 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 11:38 Stephen Rothwell [this message]
2022-05-17 13:09 ` linux-next: build warning after merge of the chrome-platform tree Muhammad Usama Anjum
2022-05-18 3:23 ` Bagas Sanjaya
2022-05-18 3:39 ` Tzung-Bi Shih
2022-05-18 4:24 ` Muhammad Usama Anjum
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 5:21 Stephen Rothwell
2021-08-30 7:21 ` Stephen Rothwell
2021-08-31 0:17 ` Benson Leung
2021-08-31 0:32 ` Stephen Rothwell
2019-04-16 4:30 Stephen Rothwell
2019-04-16 9:09 ` Enric Balletbo i Serra
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=20220516213832.19127535@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tzungbi@kernel.org \
--cc=usama.anjum@collabora.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;
as well as URLs for NNTP newsgroup(s).