[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d148732-c14d-4e96-f8fc-31acc8932534@collabora.com>
Date: Tue, 17 May 2022 18:09:25 +0500
From: Muhammad Usama Anjum <usama.anjum@...labora.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Benson Leung <bleung@...gle.com>,
Guenter Roeck <groeck@...omium.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: usama.anjum@...labora.com, Tzung-Bi Shih <tzungbi@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the chrome-platform tree
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
Powered by blists - more mailing lists