From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"christian.brauner@ubuntu.com" <christian.brauner@ubuntu.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"shorne@gmail.com" <shorne@gmail.com>,
"walken@google.com" <walken@google.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"jhubbard@nvidia.com" <jhubbard@nvidia.com>,
"daniel.m.jordan@oracle.com" <daniel.m.jordan@oracle.com>,
"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
"peterx@redhat.com" <peterx@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "rdunlap@infradead.org" <rdunlap@infradead.org>
Subject: Re: [PATCH] arcc/kernel/process: Few mundane typo fixes
Date: Wed, 7 Apr 2021 20:20:45 +0000 [thread overview]
Message-ID: <d90ec8a1-f719-5145-fd70-849cdac99162@synopsys.com> (raw)
In-Reply-To: <20210322125155.3401540-1-unixbhaskar@gmail.com>
On 3/22/21 5:51 AM, Bhaskar Chowdhury wrote:
> s/defintion/definition/
> s/succeded/succeeded/
> s/commiting/committing/
> s/interrutps/interrupts/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
I've squashed all your 3 patches into one (no reason to break them out)
and queued for 5.13.
Thx,
-Vineet
> ---
> diff --git a/arch/arc/kernel/process.c b/arch/arc/kernel/process.c
> index d838d0d57696..3793876f42d9 100644
> --- a/arch/arc/kernel/process.c
> +++ b/arch/arc/kernel/process.c
> @@ -50,14 +50,14 @@ SYSCALL_DEFINE3(arc_usr_cmpxchg, int *, uaddr, int, expected, int, new)
> int ret;
>
> /*
> - * This is only for old cores lacking LLOCK/SCOND, which by defintion
> + * This is only for old cores lacking LLOCK/SCOND, which by definition
> * can't possibly be SMP. Thus doesn't need to be SMP safe.
> * And this also helps reduce the overhead for serializing in
> * the UP case
> */
> WARN_ON_ONCE(IS_ENABLED(CONFIG_SMP));
>
> - /* Z indicates to userspace if operation succeded */
> + /* Z indicates to userspace if operation succeeded */
> regs->status32 &= ~STATUS_Z_MASK;
>
> ret = access_ok(uaddr, sizeof(*uaddr));
> @@ -107,7 +107,7 @@ SYSCALL_DEFINE3(arc_usr_cmpxchg, int *, uaddr, int, expected, int, new)
>
> void arch_cpu_idle(void)
> {
> - /* Re-enable interrupts <= default irq priority before commiting SLEEP */
> + /* Re-enable interrupts <= default irq priority before committing SLEEP */
> const unsigned int arg = 0x10 | ARCV2_IRQ_DEF_PRIO;
>
> __asm__ __volatile__(
> @@ -120,7 +120,7 @@ void arch_cpu_idle(void)
>
> void arch_cpu_idle(void)
> {
> - /* sleep, but enable both set E1/E2 (levels of interrutps) before committing */
> + /* sleep, but enable both set E1/E2 (levels of interrupts) before committing */
> __asm__ __volatile__("sleep 0x3 \n");
> }
>
> --
> 2.31.0
>
prev parent reply other threads:[~2021-04-07 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:51 Bhaskar Chowdhury
2021-03-22 13:23 ` Christian Brauner
2021-03-22 19:51 ` Bhaskar Chowdhury
2021-04-07 20:20 ` Vineet Gupta [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=d90ec8a1-f719-5145-fd70-849cdac99162@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=christian.brauner@ubuntu.com \
--cc=daniel.m.jordan@oracle.com \
--cc=jhubbard@nvidia.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=peterx@redhat.com \
--cc=rdunlap@infradead.org \
--cc=shorne@gmail.com \
--cc=tsbogend@alpha.franken.de \
--cc=unixbhaskar@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.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
all inboxes | Powered by JetHome®