All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, josh@joshtriplett.org,
	konstantin@linuxfoundation.org, linux-kernel@vger.kernel.org,
	rostedt@goodmis.org, workflows@vger.kernel.org, joe@perches.com,
	rdunlap@infradead.org
Subject: Re: [PATCH v4] README: restructure with role-based documentation and guidelines
Date: Wed, 19 Nov 2025 14:34:40 -0800	[thread overview]
Message-ID: <202511191434.9CA5301@keescook> (raw)
In-Reply-To: <20251119023832.1095490-1-sashal@kernel.org>

On Tue, Nov 18, 2025 at 09:38:32PM -0500, 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>
> ---
> 
> Changes since v3:
> 
>  - No AI hype :)
>  - Link to a guide for building the kernel

Thanks! With the other comments in the v4 thread fixed:

Reviewed-by: Kees Cook <kees@kernel.org>

-Kees

-- 
Kees Cook

      parent reply	other threads:[~2025-11-19 22:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  2:38 [PATCH v4] README: restructure with role-based documentation and guidelines Sasha Levin
2025-11-19  6:10 ` Randy Dunlap
2025-11-19  7:43 ` Mauro Carvalho Chehab
2025-11-19 15:48   ` Sasha Levin
2025-11-19 22:34 ` Kees Cook [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=202511191434.9CA5301@keescook \
    --to=kees@kernel.org \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=josh@joshtriplett.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.