All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
	kernel test robot <rong.a.chen@intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h':  111< /* free                                    ( 3*32+29) */
Date: Tue, 8 Jun 2021 20:46:02 +0200	[thread overview]
Message-ID: <YL+66gKKW5CQjq5f@zn.tnic> (raw)
In-Reply-To: <YL+xwYq8LNLY6ePU@kernel.org>

On Tue, Jun 08, 2021 at 03:06:57PM -0300, Arnaldo Carvalho de Melo wrote:
> > Or, if we start doing that then they don't have to do anything.
> 
> Who? Previously its me doing this work, i.e. keeping things in synch.
> Actually it is expected that people doing the kernel work don't touch
> tools/ wrt adding the copy,

Ok, I think I'm totally confused. First you say that you're trying to
keep the headers in sync and now you say that patches adding stuff to
the kernel cpufeatures.h header should not touch the copy in tools/...

In any case, I was thinking that we could document what people touching
cpufeatures.h need to do and put it Documentation/x86/cpuinfo.rst.

And then spread the load by asking everyone to do that test and fix the
perf build accordingly.

So that you don't have to do it all by yourself.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@suse.de>
To: kbuild-all@lists.01.org
Subject: Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h': 111< /* free ( 3*32+29) */
Date: Tue, 08 Jun 2021 20:46:02 +0200	[thread overview]
Message-ID: <YL+66gKKW5CQjq5f@zn.tnic> (raw)
In-Reply-To: <YL+xwYq8LNLY6ePU@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Tue, Jun 08, 2021 at 03:06:57PM -0300, Arnaldo Carvalho de Melo wrote:
> > Or, if we start doing that then they don't have to do anything.
> 
> Who? Previously its me doing this work, i.e. keeping things in synch.
> Actually it is expected that people doing the kernel work don't touch
> tools/ wrt adding the copy,

Ok, I think I'm totally confused. First you say that you're trying to
keep the headers in sync and now you say that patches adding stuff to
the kernel cpufeatures.h header should not touch the copy in tools/...

In any case, I was thinking that we could document what people touching
cpufeatures.h need to do and put it Documentation/x86/cpuinfo.rst.

And then spread the load by asking everyone to do that test and fix the
perf build accordingly.

So that you don't have to do it all by yourself.

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

  reply	other threads:[~2021-06-08 18:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  9:41 [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h': 111< /* free ( 3*32+29) */ kernel test robot
2021-06-02  9:41 ` kernel test robot
2021-06-02  9:45 ` Borislav Petkov
2021-06-02  9:45   ` Borislav Petkov
2021-06-02 15:35   ` Arnaldo Carvalho de Melo
2021-06-02 15:35     ` Arnaldo Carvalho de Melo
2021-06-03  7:43     ` Rong Chen
2021-06-03  7:43       ` Rong Chen
2021-06-03 21:25     ` Borislav Petkov
2021-06-03 21:25       ` Borislav Petkov
2021-06-08 17:07       ` Arnaldo Carvalho de Melo
2021-06-08 17:07         ` Arnaldo Carvalho de Melo
2021-06-08 17:38         ` Borislav Petkov
2021-06-08 17:38           ` Borislav Petkov
2021-06-08 18:06           ` Arnaldo Carvalho de Melo
2021-06-08 18:06             ` Arnaldo Carvalho de Melo
2021-06-08 18:46             ` Borislav Petkov [this message]
2021-06-08 18:46               ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2021-06-01 20:10 kernel test robot

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=YL+66gKKW5CQjq5f@zn.tnic \
    --to=bp@suse.de \
    --cc=acme@kernel.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rong.a.chen@intel.com \
    --cc=x86@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 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.