From: Will Deacon <will@kernel.org>
To: 韩科才 <hankecai@vivo.com>
Cc: trivial@kernel.org, kernel@vivo.com, catalin.marinas@arm.com,
linux-kernel@vger.kernel.org, alexios.zavras@intel.com,
broonie@kernel.org, allison@lohutok.net, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: fix spelling mistake "ca not" -> "cannot"
Date: Tue, 17 Mar 2020 22:28:47 +0000 [thread overview]
Message-ID: <20200317222846.GI20788@willie-the-truck> (raw)
In-Reply-To: <AOoADQCXCJCLyVN7qh-tYqrl.1.1584244879067.Hmail.hankecai@vivo.com>
On Sun, Mar 15, 2020 at 12:01:19PM +0800, 韩科才 wrote:
> There is a spelling mistake in the comment, Fix it.
>
> Signed-off-by: hankecai <hankecai@bbktel.com>
> ---
> arch/arm64/lib/strcmp.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/lib/strcmp.S b/arch/arm64/lib/strcmp.S
> index 4767540d1b94..4e79566726c8 100644
> --- a/arch/arm64/lib/strcmp.S
> +++ b/arch/arm64/lib/strcmp.S
> @@ -186,7 +186,7 @@ CPU_LE( rev data2, data2 )
> * as carry-propagation can corrupt the upper bits if the trailing
> * bytes in the string contain 0x01.
> * However, if there is no NUL byte in the dword, we can generate
> - * the result directly. We ca not just subtract the bytes as the
> + * the result directly. We cannot just subtract the bytes as the
> * MSB might be significant.
> */
> CPU_BE( cbnz has_nul, 1f )
Acked-by: Will Deacon <will@kernel.org>
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-03-17 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 4:01 [PATCH] arm64: fix spelling mistake "ca not" -> "cannot" 韩科才
2020-03-17 22:28 ` Will Deacon [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=20200317222846.GI20788@willie-the-truck \
--to=will@kernel.org \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=hankecai@vivo.com \
--cc=kernel@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=trivial@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