From: Masami Hiramatsu <mhiramat@kernel.org>
To: Jinbum Park <jinb.park7@gmail.com>
Cc: ananth@linux.vnet.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk
Subject: Re: [PATCH] kprobes: fix a comment typo
Date: Thu, 16 Jun 2016 06:33:49 +0900 [thread overview]
Message-ID: <20160616063349.f9406a9b343f8eab04e27931@kernel.org> (raw)
In-Reply-To: <20160615151922.GA30806@pjb1027-Latitude-E5410>
On Thu, 16 Jun 2016 00:19:22 +0900
Jinbum Park <jinb.park7@gmail.com> wrote:
> Just fix a typo in the code comment.
Thanks :)
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
>
> Signed-off-by: Jinbum Park <jinb.park7@gmail.com>
> ---
> arch/arm/probes/kprobes/opt-arm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/probes/kprobes/opt-arm.c b/arch/arm/probes/kprobes/opt-arm.c
> index bcdecc2..073c0ba 100644
> --- a/arch/arm/probes/kprobes/opt-arm.c
> +++ b/arch/arm/probes/kprobes/opt-arm.c
> @@ -223,7 +223,7 @@ int arch_prepare_optimized_kprobe(struct optimized_kprobe *op, struct kprobe *or
> *
> * So the maximum forward branch should be:
> * (0x007fffff << 2) = 0x01fffffc = 0x1fffffc
> - * The maximum backword branch should be:
> + * The maximum backward branch should be:
> * (0xff800000 << 2) = 0xfe000000 = -0x2000000
> *
> * We can simply check (rel & 0xfe000003):
> --
> 1.9.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2016-06-15 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 15:19 Jinbum Park
2016-06-15 21:33 ` Masami Hiramatsu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-29 14:42 Jinbum Park
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=20160616063349.f9406a9b343f8eab04e27931@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=jinb.park7@gmail.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
all inboxes | Powered by JetHome®