linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [FYI][PATCH 1/1] tools headers UAPI: Sync s390 syscall table file changed by new futex_waitv syscall Reply-To:
Date: Fri, 26 Nov 2021 10:53:07 +0100	[thread overview]
Message-ID: <YaCug8LEHYmZ9G6E@osiris> (raw)
In-Reply-To: <YZ/2qRW/TScYTP1U@kernel.org>

Hi Arnaldo,

> To pick the changes in this cset:
> 
>   6c122360cf2f4c5a ("s390: wire up sys_futex_waitv system call")
> 
> That add support for this new syscall in tools such as 'perf trace'.
...
> This addresses this perf build warnings:
> 
>   Warning: Kernel ABI header at 'tools/perf/arch/s390/entry/syscalls/syscall.tbl' differs from latest version at 'arch/s390/kernel/syscalls/syscall.tbl'
>   diff -u tools/perf/arch/s390/entry/syscalls/syscall.tbl arch/s390/kernel/syscalls/syscall.tbl
> 
> Cc: Heiko Carstens <hca@linux.ibm.com>
> Cc: Vasily Gorbik <gor@linux.ibm.com>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> ---
>  tools/perf/arch/s390/entry/syscalls/syscall.tbl | 1 +
>  1 file changed, 1 insertion(+)

I can happily pick this up for the s390 tree, but I'm not sure if that
is want you want?

  reply	other threads:[~2021-11-26  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 20:48 [FYI][PATCH 1/1] tools headers UAPI: Sync s390 syscall table file changed by new futex_waitv syscall Reply-To: Arnaldo Carvalho de Melo
2021-11-26  9:53 ` Heiko Carstens [this message]
2021-11-26 10:01   ` Arnaldo Carvalho de Melo
2021-11-26 11:29     ` Heiko Carstens
2021-11-26 18:50       ` 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=YaCug8LEHYmZ9G6E@osiris \
    --to=hca@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=gor@linux.ibm.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).