All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Set the field name for subsystem profile section
Date: Mon, 19 Feb 2024 14:52:39 -0700	[thread overview]
Message-ID: <87il2km89k.fsf@meer.lwn.net> (raw)
In-Reply-To: <20240216201902.10095-1-sj@kernel.org>

SeongJae Park <sj@kernel.org> writes:

> Subsystem profile section entry identifier is not having its field name
> that can be parsed by maintainers_include.py, unlike other sections
> which have their own human-readable field names.  As a result, profile
> sections on rendered rst file is having weird name, 'P:'.  Set the field
> name as 'Subsystem Profile'.
>
> Fixes: 4699c504e603 ("Maintainer Handbook: Maintainer Entry Profile")
> Signed-off-by: SeongJae Park <sj@kernel.org>
> ---
>  MAINTAINERS | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8d1052fa6a69..25fa30bec35f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24,7 +24,7 @@ Descriptions of section entries and preferred order
>  	   filing info, a direct bug tracker link, or a mailto: URI.
>  	C: URI for *chat* protocol, server and channel where developers
>  	   usually hang out, for example irc://server/channel.
> -	P: Subsystem Profile document for more details submitting
> +	P: *Subsystem Profile* document for more details submitting
>  	   patches to the given subsystem. This is either an in-tree file,

Applied, thanks.

jon

      reply	other threads:[~2024-02-19 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 20:19 [PATCH] MAINTAINERS: Set the field name for subsystem profile section SeongJae Park
2024-02-19 21:52 ` Jonathan Corbet [this message]

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=87il2km89k.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj@kernel.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 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.