linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Hans de Goede <hdegoede@redhat.com>, Mark Gross <mark.gross@intel.com>
Cc: Divya Bharathi <divya.bharathi@dell.com>,
	Mario Limonciello <mario.limonciello@dell.com>,
	Prasanth KSR <prasanth.ksr@dell.com>,
	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 drivers-x86 tree
Date: Thu, 5 Nov 2020 17:55:07 +1100	[thread overview]
Message-ID: <20201105175507.5f59883b@canb.auug.org.au> (raw)

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

Hi all,

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

Documentation/ABI/testing/sysfs-class-firmware-attributes:2: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-firmware-attributes:2: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-firmware-attributes:2: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/ABI/testing/sysfs-class-firmware-attributes:173: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-firmware-attributes:173: WARNING: Unexpected indentation.
Documentation/ABI/testing/sysfs-class-firmware-attributes:173: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/ABI/testing/sysfs-class-firmware-attributes:111: WARNING: Inline emphasis start-string without end-string.

Introduced by commit

  e8a60aa7404b ("platform/x86: Introduce support for Systems Management Driver over WMI for Dell Systems")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-11-05  6:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  6:55 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-22  2:54 linux-next: build warnings after merge of the drivers-x86 tree 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
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
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=20201105175507.5f59883b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=divya.bharathi@dell.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=mark.gross@intel.com \
    --cc=prasanth.ksr@dell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).