Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 31 Oct 2022 11:50:03 +0000
From:   Mark Rutland <mark.rutland@arm.com>
To:     Bagas Sanjaya <bagasdotme@gmail.com>
Cc:     Mukesh Ojha <quic_mojha@quicinc.com>, catalin.marinas@arm.com,
        will@kernel.org, broonie@kernel.org, linux-kernel@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: entry: Fix typo
Message-ID: <Y1+2a1syAdi2R7xD@FVFF77S0Q05N>
References: <1667027268-1255-1-git-send-email-quic_mojha@quicinc.com>
 <Y10sNSE6/B2p95+I@debian.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y10sNSE6/B2p95+I@debian.me>
Precedence: bulk

On Sat, Oct 29, 2022 at 08:35:49PM +0700, Bagas Sanjaya wrote:
> On Sat, Oct 29, 2022 at 12:37:48PM +0530, Mukesh Ojha wrote:
> >  /*
> >   * Handle IRQ/context state management when exiting a debug exception from
> >   * kernel mode. After this function returns it is not safe to call regular
> > - * kernel code, intrumentable code, or any code which may trigger an exception.
> > + * kernel code, instrumentable code, or any code which may trigger an exception.
> >   */
> >  static void noinstr arm64_exit_el1_dbg(struct pt_regs *regs)
> >  {
> 
> What about "... it is unsafe to call regular kernel, instrumentable, or
> any other code ..." instead?

I much prefer this as-is, but with the typo fixed.

Thanks,
Mark.