From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Borislav Petkov <bp@suse.de>
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 15:06:57 -0300 [thread overview]
Message-ID: <YL+xwYq8LNLY6ePU@kernel.org> (raw)
In-Reply-To: <YL+rEhU4A1tXNFYO@zn.tnic>
Em Tue, Jun 08, 2021 at 07:38:26PM +0200, Borislav Petkov escreveu:
> On Tue, Jun 08, 2021 at 02:07:36PM -0300, Arnaldo Carvalho de Melo wrote:
> > Apply the patch, try to build it, it doesn't matter where you build it,
> > only that after applying the patch I want to know if it doersn't build,
> > so that I can look at it earlier than when it gets to my attention by
> > merging upstream, etc.
>
> I believe if you give the 0day guys a step-by-step what to do, they'll
> probably add it to the lineup. :)
I think I already did it in a another e-mail.
> > We're doing it already, Peter wants to help me with it, and I think this
> > has value.
> 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, there is value in the warning, in looking at
what changed, to see if we should change tooling in some way beyond what
automation in merely making the copy can possibly do.
What has value is checking that the process of addressing the out of
sync warning doesn't break the build, to point to things that will need
human work to get it back to a buildable state.
> --
> Regards/Gruss,
> Boris.
>
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
--
- Arnaldo
next prev parent reply other threads:[~2021-06-08 18:07 UTC|newest]
Thread overview: 9+ 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:45 ` Borislav Petkov
2021-06-02 15:35 ` Arnaldo Carvalho de Melo
2021-06-03 7:43 ` Rong Chen
2021-06-03 21:25 ` Borislav Petkov
2021-06-08 17:07 ` Arnaldo Carvalho de Melo
2021-06-08 17:38 ` Borislav Petkov
2021-06-08 18:06 ` Arnaldo Carvalho de Melo [this message]
2021-06-08 18:46 ` Borislav Petkov
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+xwYq8LNLY6ePU@kernel.org \
--to=acme@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--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 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).