From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: frederic@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel: Change word in comment to a correct form to convey the meaning
Date: Mon, 8 Jun 2026 05:53:01 +0530 [thread overview]
Message-ID: <aiYLZRSJ3hfQpot7_Gentoo@unixbhaskar-laptop> (raw)
In-Reply-To: <0f644d83-db26-484f-9227-1028e7decd4f@paulmck-laptop>
On 16:55 Sun 07 Jun 2026, Paul E. McKenney wrote:
>On Mon, Jun 08, 2026 at 04:07:19AM +0530, Bhaskar Chowdhury wrote:
>> s/irreproducibly/irreproducible/
>>
>> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
>> ---
>> kernel/context_tracking.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/context_tracking.c b/kernel/context_tracking.c
>> index a743e7ffa6c0..fda4ec211963 100644
>> --- a/kernel/context_tracking.c
>> +++ b/kernel/context_tracking.c
>> @@ -332,7 +332,7 @@ EXPORT_SYMBOL_GPL(ct_idle_exit);
>> * If your architecture's idle loop does do upcalls to user mode (or does
>> * anything else that results in unbalanced calls to the irq_enter() and
>> * irq_exit() functions), RCU will give you what you deserve, good and hard.
>> - * But very infrequently and irreproducibly.
>> + * But very infrequently and irreproducible.
>
>OK, I will bite... Don't both these words need to be in adverb form?
>What am I missing?
>
I think I missed the mark and misconceived. Sorry about the noise.
> Thanx, Paul
>
>> *
>> * Use things like work queues to work around this limitation.
>> *
>> --
>> 2.53.0
>>
--
Thanks,
Bhaskar
"Here's looking at you kid"-- Casablanca
https://about.me/unixbhaskar
next prev parent reply other threads:[~2026-06-08 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 22:37 Bhaskar Chowdhury
2026-06-07 23:55 ` Paul E. McKenney
2026-06-08 0:23 ` Bhaskar Chowdhury [this message]
2026-06-08 1:40 ` Paul E. McKenney
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=aiYLZRSJ3hfQpot7_Gentoo@unixbhaskar-laptop \
--to=unixbhaskar@gmail.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
all inboxes | Powered by JetHome®