All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Borislav Petkov <bp@suse.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: Thu, 3 Jun 2021 23:25:05 +0200	[thread overview]
Message-ID: <YLlIsS1brAdNyG4K@zn.tnic> (raw)
In-Reply-To: <YLelUPtti40D7DUl@kernel.org>

On Wed, Jun 02, 2021 at 12:35:44PM -0300, Arnaldo Carvalho de Melo wrote:
> ... 
> will build in older systems where things added to the updated copy of
> the kernel headers isn't present, so trying to update the file and then
> rebuild perf, only warning me if it doesn't build would give me an early
> warning about things that are breaking and that I should look sooner
> rather than later.
> 
> 	Doing just the diff is not that useful :-)

Lemme see if I understand this correctly: you'd like for the 0day folks
to take those perf-*src-pkg builds, put them on an *old* distro and see
if it builds. Am I close?

And do that with the headers in tools/ which do not have the new changes
and see if they still build?

Or?

Alternatively, we can always go back to keeping the headers in sync with
those in tools/ and f'get about it.

Thoughts?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.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: Thu, 03 Jun 2021 23:25:05 +0200	[thread overview]
Message-ID: <YLlIsS1brAdNyG4K@zn.tnic> (raw)
In-Reply-To: <YLelUPtti40D7DUl@kernel.org>

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

On Wed, Jun 02, 2021 at 12:35:44PM -0300, Arnaldo Carvalho de Melo wrote:
> ... 
> will build in older systems where things added to the updated copy of
> the kernel headers isn't present, so trying to update the file and then
> rebuild perf, only warning me if it doesn't build would give me an early
> warning about things that are breaking and that I should look sooner
> rather than later.
> 
> 	Doing just the diff is not that useful :-)

Lemme see if I understand this correctly: you'd like for the 0day folks
to take those perf-*src-pkg builds, put them on an *old* distro and see
if it builds. Am I close?

And do that with the headers in tools/ which do not have the new changes
and see if they still build?

Or?

Alternatively, we can always go back to keeping the headers in sync with
those in tools/ and f'get about it.

Thoughts?

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  parent reply	other threads:[~2021-06-03 21:25 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 [this message]
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
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=YLlIsS1brAdNyG4K@zn.tnic \
    --to=bp@alien8.de \
    --cc=acme@kernel.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@suse.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.