From: Greg KH <gregkh@linuxfoundation.org>
To: Pranav Tyagi <pranav.tyagi03@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel-mentees@lists.linux.dev,
skhan@linuxfoundation.org
Subject: Re: [PATCH] documentation grammer correction
Date: Mon, 3 Feb 2025 17:23:42 +0100 [thread overview]
Message-ID: <2025020359-despise-polyester-f8e4@gregkh> (raw)
In-Reply-To: <20250203161920.14028-1-pranav.tyagi03@gmail.com>
On Mon, Feb 03, 2025 at 09:49:20PM +0530, Pranav Tyagi wrote:
> I am submitting this patch as a part of lfx mentorship application tasks.
> This patch contains grammatical and spelling corrections in the linux
> documentation. Please let me know if any further clarification is
> required.
Lots of information here in the text that doesn't need to be :)
Please read the kernel documentation for how to write a good changelog
text, many times it is the hardest part of creating a valid patch.
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-03 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 16:19 [PATCH] documentation grammer correction Pranav Tyagi
2025-02-03 16:23 ` Greg KH [this message]
2025-02-03 16:47 ` Khalid Masum
-- strict thread matches above, loose matches on Subject: below --
2025-01-31 17:47 Pranav Tyagi
2025-02-01 8:43 ` Greg KH
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=2025020359-despise-polyester-f8e4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=pranav.tyagi03@gmail.com \
--cc=skhan@linuxfoundation.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.