linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
	christophe.leroy@csgroup.eu, npiggin@gmail.com,
	jniethe5@gmail.com, alistair@popple.id.au, mikey@neuling.org,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch: powerpc: kernel: Change droping to dropping in the file traps.c
Date: Wed, 24 Feb 2021 08:24:09 -0800	[thread overview]
Message-ID: <7b810bb2-4704-4882-79ce-3e41efc9ea55@infradead.org> (raw)
In-Reply-To: <20210224075547.763063-1-unixbhaskar@gmail.com>

On 2/23/21 11:55 PM, Bhaskar Chowdhury wrote:
> 
> s/droping/dropping/
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>

Acked-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  arch/powerpc/kernel/traps.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
> index 1583fd1c6010..83a53b67412a 100644
> --- a/arch/powerpc/kernel/traps.c
> +++ b/arch/powerpc/kernel/traps.c
> @@ -405,7 +405,7 @@ void hv_nmi_check_nonrecoverable(struct pt_regs *regs)
>  	 * Now test if the interrupt has hit a range that may be using
>  	 * HSPRG1 without having RI=0 (i.e., an HSRR interrupt). The
>  	 * problem ranges all run un-relocated. Test real and virt modes
> -	 * at the same time by droping the high bit of the nip (virt mode
> +	 * at the same time by dropping the high bit of the nip (virt mode
>  	 * entry points still have the +0x4000 offset).
>  	 */
>  	nip &= ~0xc000000000000000ULL;
> --
> 2.30.1
> 


-- 
~Randy


  reply	other threads:[~2021-02-24 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  7:55 [PATCH] arch: powerpc: kernel: Change droping to dropping in the file traps.c Bhaskar Chowdhury
2021-02-24 16:24 ` Randy Dunlap [this message]
2021-03-31  1:09 ` Michael Ellerman

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=7b810bb2-4704-4882-79ce-3e41efc9ea55@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=jniethe5@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.org \
    --cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).