[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c2edab0f-3351-42fb-84d4-f588ce6dcd9a@infradead.org>
Date: Sun, 7 Dec 2025 09:42:42 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: ᴋᴀʀᴛɪᴋ sʜᴀʜ
<kartikpro9599@...il.com>, linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] docs: improve introduction wording in howto.rst
On 12/7/25 1:37 AM, ᴋᴀʀᴛɪᴋ sʜᴀʜ wrote:
> From 56985c72f365c7f0e9ba8ae66ba99c198c15128c Mon Sep 17 00:00:00 2001
> From: kartikpro9599-hash <kartikpro9599@...il.com>
> Date: Sun, 7 Dec 2025 13:53:02 +0530
> Subject: [PATCH v4] docs: improve introduction wording in howto.rst
>
The new text looks good to me. However, each patch should have a patch
description between the Subject: and the Signed-off-by: lines.
See https://docs.kernel.org/process/submitting-patches.html#describe-your-changes
if you need more info on this.
> Signed-off-by: kartikpro9599-hash <kartikpro9599@...il.com>
> ---
> Documentation/process/howto.rst | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/process/howto.rst b/Documentation/process/howto.rst
> index 9438e03d6..dd840115f 100644
> --- a/Documentation/process/howto.rst
> +++ b/Documentation/process/howto.rst
> @@ -3,11 +3,11 @@
> HOWTO do Linux kernel development
> =================================
>
> -This is the be-all, end-all document on this topic. It contains
> -instructions on how to become a Linux kernel developer and how to learn
> -to work with the Linux kernel development community. It tries to not
> -contain anything related to the technical aspects of kernel programming,
> -but will help point you in the right direction for that.
> +This is a complete introductory document on this topic. It
> +contains instructions on how to become a Linux kernel developer
> +and how to work with the Linux kernel development community. It
> +does not cover the technical aspects of kernel programming, but
> +will help point you in the right direction for that.
>
> If anything in this document becomes out of date, please send in patches
> to the maintainer of this file, who is listed at the bottom of the
--
~Randy
Powered by blists - more mailing lists