From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: valdis.kletnieks@vt.edu, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: next-20180416 - warnings from 'make tools/perf'
Date: Mon, 23 Apr 2018 11:55:37 -0300 [thread overview]
Message-ID: <20180423145537.GJ30324@kernel.org> (raw)
In-Reply-To: <20180423065204.cgzu7mvivrph3gfw@gmail.com>
Em Mon, Apr 23, 2018 at 08:52:04AM +0200, Ingo Molnar escreveu:
>
> * valdis.kletnieks@vt.edu <valdis.kletnieks@vt.edu> wrote:
>
> > Seeing these warnings. 'diff' tells me that the files
> > are in fact significantly different.
> >
> > Warning: Kernel ABI header at 'tools/include/uapi/linux/kvm.h' differs from latest version at 'include/uapi/linux/kvm.h'
> > Warning: Kernel ABI header at 'tools/include/uapi/linux/prctl.h' differs from latest version at 'include/uapi/linux/prctl.h'
> > Warning: Kernel ABI header at 'tools/include/uapi/sound/asound.h' differs from latest version at 'include/uapi/sound/asound.h'
> > Warning: Kernel ABI header at 'tools/arch/x86/include/asm/required-features.h' differs from latest version at 'arch/x86/include/asm/required-features.h'
> > Warning: Kernel ABI header at 'tools/arch/x86/include/uapi/asm/kvm.h' differs from latest version at 'arch/x86/include/uapi/asm/kvm.h'
> > Warning: Kernel ABI header at 'tools/arch/arm/include/uapi/asm/kvm.h' differs from latest version at 'arch/arm/include/uapi/asm/kvm.h'
> > Warning: Kernel ABI header at 'tools/include/uapi/asm-generic/mman-common.h' differs from latest version at 'include/uapi/asm-generic/mman-common.h'
> > Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h'
> > Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h'
>
> The warnings are harmless, and they should be fixed in v4.17-rc2.
Yeah, its just a way for us to get warned that new APIs were introduced,
so we need to check if changes are needed in the tools, sometimes those
changes take place automagically when we update the copies we have.
We're not expecting or asking anybody to care about tools/ when doing
changes in kernel headers that we have copies, that would possibly annoy
kernel developers and we want to keep them super happy and productive
:-)
- Arnaldo
next prev parent reply other threads:[~2018-04-23 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 5:52 next-20180416 - warnings from 'make tools/perf' valdis.kletnieks
2018-04-23 6:52 ` Ingo Molnar
2018-04-23 14:55 ` Arnaldo Carvalho de Melo [this message]
2018-04-23 17:56 ` valdis.kletnieks
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=20180423145537.GJ30324@kernel.org \
--to=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valdis.kletnieks@vt.edu \
/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