From: Shuah Khan <skhan@linuxfoundation.org>
To: Rahul Kumar <rk0006818@gmail.com>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests: timers: Fix grammar and clarify comments in nanosleep.c
Date: Thu, 22 May 2025 15:52:23 -0600 [thread overview]
Message-ID: <d1908709-dc6e-48cf-8a94-d03e173c6cea@linuxfoundation.org> (raw)
In-Reply-To: <20250514222112.396705-1-rk0006818@gmail.com>
On 5/14/25 16:21, Rahul Kumar wrote:
> Improved the clarity and grammar in the header comment of nanosleep.c
> for better readability and consistency with kernel documentation style.
This patch isn't really fixing anything. I won't be taking this one.
Sorry.
thanks,
-- Shuah
prev parent reply other threads:[~2025-05-22 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 22:21 [PATCH] selftests: timers: Fix grammar and clarify comments in nanosleep.c Rahul Kumar
2025-05-22 21:52 ` Shuah Khan [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=d1908709-dc6e-48cf-8a94-d03e173c6cea@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rk0006818@gmail.com \
/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