From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tony Luck <tony.luck@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the origin tree
Date: Mon, 25 Mar 2024 12:17:50 +1100 [thread overview]
Message-ID: <20240325121750.265d655c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi all,
Building Linus' tree, today's linux-next build (htmldocs) produced
this warning:
Documentation/arch/x86/resctrl.rst:577: WARNING: Title underline too short.
Memory bandwidth Allocation specified in MiBps
---------------------------------------------
Introduced by commit
a8ed59a3a8de ("Documentation/x86: Document that resctrl bandwidth control units are MiB")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-03-25 1:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 1:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 6:03 linux-next: build warning after merge of the origin tree Stephen Rothwell
2025-01-22 10:00 ` Akira Yokosawa
2025-01-22 13:39 ` Bagas Sanjaya
2025-01-22 14:46 ` Akira Yokosawa
2025-01-23 0:27 ` Bagas Sanjaya
2025-01-22 21:57 ` Stephen Rothwell
2022-01-17 0:45 Stephen Rothwell
2022-01-17 1:27 ` Suren Baghdasaryan
2022-01-17 2:24 ` Stephen Rothwell
2022-01-17 22:01 ` Andrew Morton
2021-01-06 22:05 Stephen Rothwell
2021-01-06 22:23 ` Johannes Berg
2021-01-06 22:44 ` Stephen Rothwell
2021-01-06 22:46 ` Johannes Berg
2021-01-06 23:20 ` Stephen Rothwell
2019-11-27 20:59 Stephen Rothwell
2019-11-28 8:11 ` Linus Walleij
2012-05-14 0:44 Stephen Rothwell
2012-05-14 3:00 ` David Miller
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=20240325121750.265d655c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
/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