From: Hans de Goede <hdegoede@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Mark Gross <markgross@kernel.org>
Cc: "David E. Box" <david.e.box@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the drivers-x86 tree
Date: Thu, 24 Mar 2022 08:39:19 +0100 [thread overview]
Message-ID: <2f33bdce-a002-708a-dd65-7bfb6ebc4cd9@redhat.com> (raw)
In-Reply-To: <20220324183329.22c97ea1@canb.auug.org.au>
Hi,
On 3/24/22 08:33, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 1 Mar 2022 20:16:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the drivers-x86 tree, today's linux-next build (htmldocs)
>> produced these warnings:
>>
>> Documentation/ABI/testing/sysfs-driver-intel_sdsi:2: WARNING: Unexpected indentation.
>> Documentation/ABI/testing/sysfs-driver-intel_sdsi:2: WARNING: Block quote ends without a blank line; unexpected unindent.
>> Documentation/ABI/testing/sysfs-driver-intel_sdsi:2: WARNING: Definition list ends without a blank line; unexpected unindent.
>>
>> Introduced by commit
>>
>> 2546c6000430 ("platform/x86: Add Intel Software Defined Silicon driver")
>
> I am still seeing these warnings.
I replied to your original report on March 1st, but I never got a reply
to my reply:
"""
Thank you for the report.
So I just did:
touch Documentation/ABI/testing/sysfs-driver-intel_sdsi
make htmldocs &> log
In a repo with drivers-x86/for-next checked out and checked the generated log files.
But I'm not seeing these WARNINGs.
Also 'find Documentation/output/ -name "*sdsi*"' does not output anything,
is there anything special (maybe some extra utilities?) which I need to also enable
building of htmldocs for the files in Documentation/ABI ?
"""
If someone can let me know how to reproduce these warnings I would be happy
to fix them.
Regards,
Hans
next prev parent reply other threads:[~2022-03-24 7:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 9:16 linux-next: build warnings after merge of the drivers-x86 tree Stephen Rothwell
2022-03-01 13:53 ` Hans de Goede
2022-03-24 7:33 ` Stephen Rothwell
2022-03-24 7:39 ` Hans de Goede [this message]
2022-03-24 11:22 ` Stephen Rothwell
2022-03-24 13:01 ` Hans de Goede
2022-03-24 13:04 ` Hans de Goede
2022-03-24 21:55 ` Stephen Rothwell
2022-03-25 5:27 ` Mauro Carvalho Chehab
2022-03-25 6:18 ` Mauro Carvalho Chehab
2022-03-25 7:23 ` [PATCH] docs: kernel_abi.py: add sphinx build dependencies Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 5:30 linux-next: build warnings after merge of the drivers-x86 tree Stephen Rothwell
2023-12-22 2:54 Stephen Rothwell
2023-12-22 14:10 ` Hans de Goede
2023-03-09 1:28 Stephen Rothwell
2023-03-09 8:48 ` Hans de Goede
2023-03-09 10:40 ` Orlando Chamberlain
2021-10-21 7:47 Stephen Rothwell
2021-10-21 9:07 ` Vadim Pasternak
2021-10-21 20:04 ` Stephen Rothwell
2021-10-21 21:10 ` Jonathan Corbet
2021-10-22 9:02 ` Hans de Goede
2021-10-21 9:14 ` Hans de Goede
2021-10-21 20:02 ` Stephen Rothwell
2020-11-05 6:55 Stephen Rothwell
2011-02-22 5:13 Stephen Rothwell
2011-02-22 10:36 ` Colin Ian King
2010-12-08 2:32 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=2f33bdce-a002-708a-dd65-7bfb6ebc4cd9@redhat.com \
--to=hdegoede@redhat.com \
--cc=david.e.box@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=sfr@canb.auug.org.au \
/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