From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Benson Leung <bleung@google.com>,
Guenter Roeck <groeck@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: 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: Re: linux-next: build warning after merge of the chrome-platform tree
Date: Tue, 17 May 2022 18:09:25 +0500 [thread overview]
Message-ID: <5d148732-c14d-4e96-f8fc-31acc8932534@collabora.com> (raw)
In-Reply-To: <20220516213832.19127535@canb.auug.org.au>
On 5/16/22 4:38 PM, Stephen Rothwell wrote:
> 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")
>
I've found these warnings in local build. But I'm unable to fix them.
Apparently, there doesn't seem any unexpected indentation. This kind of
same warnings have also appeared on some more files before this commit
without any reason.
--
Muhammad Usama Anjum
next prev parent reply other threads:[~2022-05-17 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 11:38 Stephen Rothwell
2022-05-17 13:09 ` Muhammad Usama Anjum [this message]
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 --
2024-06-03 3:25 Stephen Rothwell
2024-06-03 4:20 ` Tzung-Bi Shih
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=5d148732-c14d-4e96-f8fc-31acc8932534@collabora.com \
--to=usama.anjum@collabora.com \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tzungbi@kernel.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
all inboxes | Powered by JetHome®