mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: fix '*' wildcard formatting
Date: Wed, 04 Mar 2026 15:50:10 -0700	[thread overview]
Message-ID: <87o6l343bx.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260304224201.1072044-1-rdunlap@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:

> It seems that these wildcards confuse some parser (docutils, sphinx,
> or maintainers_include.py), so quote them to avoid this issue.
> Also insert a hyphen ('-') before "all files" in several places
> to make the html output easier to read.
>
> Fixes this htmldocs warning:
>
> linux-next-20260304/MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: linux-doc@vger.kernel.org
> Cc: Kees Cook <kees@kernel.org>
>
>  MAINTAINERS |   10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)

I remain unconvinced that dragging all of MAINTAINERS into the docs
build brings any joy.  Is that something that you actually use?

(That said, as long as we're doing it, it should work properly)

Thanks,

jon

  reply	other threads:[~2026-03-04 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 22:42 Randy Dunlap
2026-03-04 22:50 ` Jonathan Corbet [this message]
2026-03-05  0:24   ` Randy Dunlap
2026-03-05  9:24 ` Joe Perches
2026-03-05 21:26   ` Randy Dunlap

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=87o6l343bx.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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

all inboxes | Powered by JetHome®