From: Colin Ian King <colin.king@canonical.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Alexey Gladkov <legion@kernel.org>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] kernel/user.c: Fix spelling mistake "cpunter" -> "counter"
Date: Wed, 4 Aug 2021 14:41:05 +0100 [thread overview]
Message-ID: <481ca355-6359-b8b4-423e-54b0c6000b00@canonical.com> (raw)
In-Reply-To: <e67d1ff8-f872-c1af-7f1c-03ac9e9d7d2e@infradead.org>
On 04/08/2021 14:35, Randy Dunlap wrote:
> On 8/4/21 5:06 AM, Colin King wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> There is a spelling mistake in a panic message. Fix it.
>>
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> kernel/user.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/user.c b/kernel/user.c
>> index a2673f940506..7fc40af8d8ac 100644
>> --- a/kernel/user.c
>> +++ b/kernel/user.c
>> @@ -223,7 +223,7 @@ static int __init uid_cache_init(void)
>> INIT_HLIST_HEAD(uidhash_table + n);
>> if (percpu_counter_init(&root_user.epoll_watches, 0, GFP_KERNEL))
>> - panic("percpu cpunter alloc failed");
>> + panic("percpu counter alloc failed");
>> /* Insert the root user immediately (init already runs as
>> root) */
>> spin_lock_irq(&uidhash_lock);
>>
>
> Nick Piggin has reworded that panic message text in a patch
> yesterday so this patch isn't needed.
Fair enough. Thanks for the info.
>
> https://lore.kernel.org/lkml/1628051945.fens3r99ox.astroid@bobo.none/
>
>
> thanks.
prev parent reply other threads:[~2021-08-04 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 12:06 [PATCH][next] kernel/user.c: Fix spelling mistake "cpunter" -> "counter" Colin King
2021-08-04 13:35 ` Randy Dunlap
2021-08-04 13:41 ` Colin Ian King [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=481ca355-6359-b8b4-423e-54b0c6000b00@canonical.com \
--to=colin.king@canonical.com \
--cc=ebiederm@xmission.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).