public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>,
	Thomas Richter <tmricht@linux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: s390 unistd.h & perf
Date: Mon, 5 Feb 2018 09:16:06 +0100	[thread overview]
Message-ID: <20180205081606.GA4612@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180202162322.GF26905@kernel.org>

Hi Arnaldo,

On Fri, Feb 02, 2018 at 01:23:22PM -0300, Arnaldo Carvalho de Melo wrote:
> 
> 	I noticed, after fast forwarding my perf/urgent branch to
> torvalds/master, that this appears in my perf build:
> 
> Warning: Kernel ABI header at 'tools/arch/s390/include/uapi/asm/unistd.h' differs from latest version at 'arch/s390/include/uapi/asm/unistd.h'
> 
> 	Looking at the log for that file I noticed this cset:
> 
> 4381f9f12e79 ("s390/syscalls: use generated syscall_table.h and unistd.h header files")
> 
> 	Can you please take a look how this affects the syscall table
> generation process in tools/perf and how can we proceed to silence that
> warning, i.e. to update the copy we have in tools/?

I reworked the our system call table a bit to also have a text file containing
the system calls.  For this, I also have an update for perf.  Will post these
patches by end of this week.

Thanks and kind regards,
  Hendrik

  reply	other threads:[~2018-02-05  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 16:23 s390 unistd.h & perf Arnaldo Carvalho de Melo
2018-02-05  8:16 ` Hendrik Brueckner [this message]
2018-02-05 15:04   ` 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=20180205081606.GA4612@linux.vnet.ibm.com \
    --to=brueckner@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tmricht@linux.vnet.ibm.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