All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Denis Pauk <pauk.denis@gmail.com>,
	Ed Brindley <kernel@maidavale.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the hwmon-staging tree
Date: Wed, 24 Nov 2021 16:22:43 +1100	[thread overview]
Message-ID: <20211124162243.7db9ad02@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

Hi all,

After merging the hwmon-staging tree, today's linux-next build (htmldocs)
produced these warnings:

Documentation/hwmon/asus_wmi_sensors.rst:33: WARNING: Unexpected indentation.
Documentation/hwmon/asus_wmi_sensors.rst:68: WARNING: Unexpected indentation.
Documentation/hwmon/asus_wmi_sensors.rst:76: WARNING: Block quote ends without a blank line; unexpected unindent.

Introduced by commit

  9d07e54a25b8 ("hwmon: (asus_wmi_sensors) Support X370 Asus WMI.")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-11-24  5:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  5:22 Stephen Rothwell [this message]
2021-11-24  6:43 ` [PATCH 1/1] hwmon: Fix warnings in asus_wmi_sensors.rst documetation Denis Pauk
2021-11-24 14:13   ` Guenter Roeck
  -- strict thread matches above, loose matches on Subject: below --
2024-02-04 23:41 linux-next: build warnings after merge of the hwmon-staging tree Stephen Rothwell
2024-02-05  0:04 ` Guenter Roeck
2022-06-07  4:23 Stephen Rothwell
2022-06-07  9:35 ` Bagas Sanjaya
2022-06-07 12:39   ` Guenter Roeck
2022-06-07  4:19 Stephen Rothwell
2022-06-07  9:37 ` Bagas Sanjaya
2022-06-07 12:40   ` Guenter Roeck
2019-06-06  0: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=20211124162243.7db9ad02@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kernel@maidavale.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pauk.denis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.