public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Hans de Goede <hdegoede@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
	Mark Gross <markgross@kernel•org>
Cc: Vadim Pasternak <vadimp@nvidia•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, 21 Oct 2021 11:14:29 +0200	[thread overview]
Message-ID: <2b5929e2-eb77-d625-5637-fd8353909fda@redhat.com> (raw)
In-Reply-To: <20211021184735.794b22a7@canb.auug.org.au>

Hi Stephen,

On 10/21/21 09:47, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the drivers-x86 tree, today's linux-next build (htmldocs)
> produced these warnings:
> 
> Documentation/ABI/stable/sysfs-driver-mlxreg-io:230: WARNING: Unexpected indentation.
> Documentation/ABI/stable/sysfs-driver-mlxreg-io:230: WARNING: Block quote ends without a blank line; unexpected unindent.
> 
> Introduced by commit
> 
>   527cd54d49dd ("Documentation/ABI: Add new attributes for mlxreg-io sysfs interfaces")

Thank you for reporting this.

I've a bit of a noob question which tool / make target generates these warnings?

I would like to make sure they are fixed, but first I must be able to reproduce
them.

Regards,

Hans

next prev parent reply	other threads:[~2021-10-21  9:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  7:47 linux-next: build warnings after merge of the drivers-x86 tree 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 [this message]
2021-10-21 20:02   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-10-24  5:30 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
2022-03-01  9:16 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
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
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=2b5929e2-eb77-d625-5637-fd8353909fda@redhat.com \
    --to=hdegoede@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=markgross@kernel$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=vadimp@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox