linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: He Kuang <hekuang@huawei.com>,
	peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, jolsa@redhat.com,
	mhiramat@kernel.org, wangnan0@huawei.com,
	bintian.wang@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] perf probe: Fix wrong register name for arm64
Date: Wed, 25 Jan 2017 09:22:52 +0000	[thread overview]
Message-ID: <20170125092252.GA27026@arm.com> (raw)
In-Reply-To: <20170124191111.GH10340@kernel.org>

On Tue, Jan 24, 2017 at 04:11:11PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 24, 2017 at 10:30:14AM +0000, He Kuang escreveu:
> > The register name of arm64 architecture is x0-x31 not r0-r31, this
> > patch changes this typo.
> > 
> > Before this patch:
> 
> Will, are you ok with this one? I'll make sure I'll forward patches in
> this area to you if you're not on the CC list,

Thanks, Arnaldo. Yes, this one looks correct to me:

Acked-by: Will Deacon <will.deacon@arm.com>

Will

  reply	other threads:[~2017-01-25  9:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 10:30 [PATCH 0/2] Support bpf prologue for arm64 He Kuang
2017-01-24 10:30 ` [PATCH 1/2] perf probe: Fix wrong register name " He Kuang
2017-01-24 19:11   ` Arnaldo Carvalho de Melo
2017-01-25  9:22     ` Will Deacon [this message]
2017-01-26  1:24   ` Masami Hiramatsu
2017-01-26 15:28   ` [tip:perf/core] " tip-bot for He Kuang
2017-05-03  8:54   ` [PATCH 1/2] " Pratyush Anand
2017-01-24 10:30 ` [PATCH 2/2] perf tools: Introduce regs_query_register_offset() " He Kuang
2017-01-24 18:25   ` Will Deacon
2017-01-24 19:09     ` Arnaldo Carvalho de Melo
2017-01-25  7:23       ` [PATCH 2/2 v2] perf tools: Enable bpf prologue " He Kuang
2017-01-25 13:32         ` Will Deacon
2017-01-26  1:49           ` Masami Hiramatsu
2017-01-26 16:52             ` Will Deacon
2017-01-26 19:31               ` Arnaldo Carvalho de Melo
2017-02-03 11:08                 ` Hekuang
2017-01-26  1:51         ` Masami Hiramatsu
2017-01-25  7:26       ` [PATCH 2/2] perf tools: Introduce regs_query_register_offset() " Hekuang
2017-01-24 15:56 ` [PATCH 0/2] Support bpf prologue " Arnaldo Carvalho de Melo

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=20170125092252.GA27026@arm.com \
    --to=will.deacon@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bintian.wang@huawei.com \
    --cc=hekuang@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=wangnan0@huawei.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).