From: Jonathan Corbet <corbet@lwn.net>
To: Kalle Valo <kvalo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: MAINTAINERS: add "Profile" keyword entry name
Date: Mon, 19 Feb 2024 14:51:46 -0700 [thread overview]
Message-ID: <87jzn0m8b1.fsf@meer.lwn.net> (raw)
In-Reply-To: <87zfvwbyu3.fsf@kernel.org>
Kalle Valo <kvalo@kernel.org> writes:
> Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> writes:
>
>> The HTML output of MAINTAINERS file prints "P:" for subsystem profile,
>> e.g.:
>> Status: Maintained
>> P: process/maintainer-soc-clean-dts
>>
>> Use "Profile" as this entry name.
>>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Heh, I was confused what HTML file Krzysztof was talking about but after
> some digging I found this:
>
> https://docs.kernel.org/process/maintainers.html
>
> This is very useful! You can link directly to entries[1] and it's easy
> to read which makes it easier to talk with non-technical people.
Non-technical people like ... maintainers? :)
> Jonathan, I wish we would make this HTML version more visible, for
> example what about adding a link to the HTML version in beginning of the
> file? And maybe add a short introduction text at the same time? I can
> send a patch if there's interest.
I'll certainly entertain a patch but ... I feel like the same could be
said for any file within Documentation/. Perhaps we should make the
rendered docs on kernel.org more discoverable, but I'm not sure that the
maintainers manual is the place to start...?
Thanks,
jon
next prev parent reply other threads:[~2024-02-19 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 8:24 [PATCH v2] docs: MAINTAINERS: add "Profile" keyword entry name Krzysztof Kozlowski
2024-02-19 9:14 ` Kalle Valo
2024-02-19 21:51 ` Jonathan Corbet [this message]
2024-02-19 21:49 ` Jonathan Corbet
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=87jzn0m8b1.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kvalo@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox