From: Mukesh Ojha <mojha@codeaurora.org>
To: Colin King <colin.king@canonical.com>,
Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: kprobes: fix spelling mistake "undefeined" -> "undefined"
Date: Fri, 19 Apr 2019 00:33:46 +0530 [thread overview]
Message-ID: <c0144664-aa17-7ae1-dedb-ec2723682f56@codeaurora.org> (raw)
In-Reply-To: <20190418173857.31285-1-colin.king@canonical.com>
On 4/18/2019 11:08 PM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake on the TEST_UNSUPPORTED macro. Fix this.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> arch/arm/probes/kprobes/test-thumb.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/probes/kprobes/test-thumb.c b/arch/arm/probes/kprobes/test-thumb.c
> index b683b4517458..6841909757cd 100644
> --- a/arch/arm/probes/kprobes/test-thumb.c
> +++ b/arch/arm/probes/kprobes/test-thumb.c
> @@ -787,7 +787,7 @@ CONDITION_INSTRUCTIONS(22,
>
> TEST_UNSUPPORTED(__inst_thumb32(0xf7f08000) " @ smc #0")
>
> - TEST_UNSUPPORTED(__inst_thumb32(0xf7f0a000) " @ undefeined")
> + TEST_UNSUPPORTED(__inst_thumb32(0xf7f0a000) " @ undefined")
>
> TEST_BF( "b.w 2f")
> TEST_BB( "b.w 2b")
next prev parent reply other threads:[~2019-04-18 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 17:38 [PATCH] ARM: kprobes: fix spelling mistake "undefeined" -> "undefined" Colin King
2019-04-18 19:03 ` Mukesh Ojha [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-10 16:02 [PATCH] ARM: kprobes: fix spelling mistake: " Colin King
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=c0144664-aa17-7ae1-dedb-ec2723682f56@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).