All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
	Mark Rutland <mark.rutland@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Tiezhu Yang <yangtiezhu@loongson.cn>
Subject: Re: [PATCH 3/4] perf tools: Update powerpc's syscall.tbl
Date: Wed, 23 Dec 2020 20:54:59 +0530	[thread overview]
Message-ID: <1608737054.bq8cv7ll62.naveen@linux.ibm.com> (raw)
In-Reply-To: <20201221234755.GC433286@kernel.org>

Arnaldo Carvalho de Melo wrote:
> Em Fri, Dec 18, 2020 at 08:08:56PM +0530, Naveen N. Rao escreveu:
>> Hi Arnaldo,
>> 
>> Arnaldo Carvalho de Melo wrote:
>> > Em Fri, Dec 18, 2020 at 08:26:59AM -0300, Arnaldo Carvalho de Melo escreveu:
>> > > Em Fri, Dec 18, 2020 at 03:59:23PM +0800, Tiezhu Yang escreveu:
>> > > > This silences the following tools/perf/ build warning:
>> > > > Warning: Kernel ABI header at 'tools/perf/arch/powerpc/entry/syscalls/syscall.tbl' differs from latest version at 'arch/powerpc/kernel/syscalls/syscall.tbl'
>> > > 
>> > > Hi Ravi, Naveen,
>> > > 
>> > > 	Can I get your Reviewed-by or Acked-by for this change and the
>> > > other that adds s390's syscall.tbl to check_headers.sh so that we get
>> > 
>> > oops s/s390/powerpc/g :-)
>> > 
>> > > notified when the copy drifts, so that we can see if it still continues
>> > > working and we can get new syscalls to be supported in things like 'perf
>> > > trace'?
>> 
>> Yes, this looks good to me:
>> Reviewed-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
>> 
>> FWIW, I had posted a similar patch back in April, but glad to have this go
>> in ;)
>> http://lkml.kernel.org/r/20200220063740.785913-1-naveen.n.rao@linux.vnet.ibm.com
> 
> My bad :-\

No worries, thanks for checking on this one.

- Naveen


  reply	other threads:[~2020-12-23 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18  7:59 [PATCH 0/4] Move syscall.tbl check and update syscall.tbl for powerpc and s390 Tiezhu Yang
2020-12-18  7:59 ` [PATCH 1/4] perf tools: Move syscall.tbl check into check-headers.sh for powerpc Tiezhu Yang
2020-12-18  7:59 ` [PATCH 2/4] perf tools: Move syscall.tbl check into check-headers.sh for s390 Tiezhu Yang
2020-12-18  7:59 ` [PATCH 3/4] perf tools: Update powerpc's syscall.tbl Tiezhu Yang
2020-12-18 11:26   ` Arnaldo Carvalho de Melo
2020-12-18 11:32     ` Arnaldo Carvalho de Melo
2020-12-18 14:38       ` Naveen N. Rao
2020-12-21 23:47         ` Arnaldo Carvalho de Melo
2020-12-23 15:24           ` Naveen N. Rao [this message]
2020-12-23 16:26             ` Arnaldo Carvalho de Melo
2020-12-18  7:59 ` [PATCH 4/4] perf tools: Update s390's syscall.tbl Tiezhu Yang
2020-12-18 11:31   ` 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=1608737054.bq8cv7ll62.naveen@linux.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=yangtiezhu@loongson.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.