From: Randy Dunlap <rdunlap@infradead.org>
To: Sasha Levin <sashal@kernel.org>,
corbet@lwn.net, linux-doc@vger.kernel.org
Cc: josh@joshtriplett.org, kees@kernel.org,
konstantin@linuxfoundation.org, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, workflows@vger.kernel.org, joe@perches.com
Subject: Re: [PATCH v4] README: restructure with role-based documentation and guidelines
Date: Tue, 18 Nov 2025 22:10:32 -0800 [thread overview]
Message-ID: <74bf507d-5c29-4e9c-a6d6-afc0ec012688@infradead.org> (raw)
In-Reply-To: <20251119023832.1095490-1-sashal@kernel.org>
On 11/18/25 6:38 PM, Sasha Levin wrote:
> Reorganize README to provide targeted documentation paths for different user
> roles including developers, researchers, security experts, maintainers, and AI
> coding assistants. Add quick start section and essential docs links.
>
> Include proper attribution requirements for AI-assisted contributions using
> Assisted-by tags with agent details and tools used.
>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
I like it except the commit message needs some rework (deletions).
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
>
> Changes since v3:
>
> - No AI hype 🙂
> - Link to a guide for building the kernel
>
>
> README | 160 +++++++++++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 149 insertions(+), 11 deletions(-)
--
~Randy
next prev parent reply other threads:[~2025-11-19 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 2:38 Sasha Levin
2025-11-19 6:10 ` Randy Dunlap [this message]
2025-11-19 7:43 ` Mauro Carvalho Chehab
2025-11-19 15:48 ` Sasha Levin
2025-11-19 22:34 ` Kees Cook
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=74bf507d-5c29-4e9c-a6d6-afc0ec012688@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=workflows@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