public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Palmer Dabbelt <palmer@dabbelt•com>, Paul Walmsley <paul@pwsan•com>
Cc: Alexandre Ghiti <alexghiti@rivosinc•com>,
	Andy Chiu <andybnac@gmail•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 risc-v tree
Date: Tue, 3 Jun 2025 15:45:44 +1000	[thread overview]
Message-ID: <20250603154544.1602a8b5@canb.auug.org.au> (raw)

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

Hi all,

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

Documentation/arch/riscv/cmodx.rst:14: WARNING: Title underline too short.

CMODX in the Kernel Space
--------------------- [docutils]
Documentation/arch/riscv/cmodx.rst:43: WARNING: Title underline too short.

CMODX in the User Space
--------------------- [docutils]
Documentation/arch/riscv/cmodx.rst:43: WARNING: Title underline too short.

CMODX in the User Space
--------------------- [docutils]

Introduced by commit

  0e07200b2af6 ("riscv: Documentation: add a description about dynamic ftrace")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-06-03  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03  5:45 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-07  1:40 linux-next: build warnings after merge of the risc-v tree 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=20250603154544.1602a8b5@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=alexghiti@rivosinc$(echo .)com \
    --cc=andybnac@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=palmer@dabbelt$(echo .)com \
    --cc=paul@pwsan$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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