[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231031140504.GCZUEJkMPXSrEDh3MA@fat_crate.local>
Date: Tue, 31 Oct 2023 15:05:04 +0100
From: Borislav Petkov <bp@...en8.de>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>, peterz@...radead.org,
linux-kernel@...r.kernel.org, Yu-cheng Yu <yu-cheng.yu@...el.com>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Kees Cook <keescook@...omium.org>,
Mike Rapoport <rppt@...nel.org>,
Pengfei Xu <pengfei.xu@...el.com>,
John Allen <john.allen@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] x86: Let AS_WRUSS depend on X86_64
On Tue, Oct 31, 2023 at 02:59:39PM +0100, Jiri Slaby wrote:
> As I wrote, we have a config which maintainers feed through oldconfig when
> updating the kernel. This time we got WRUSS=y. It was stored in git and
> later passed to build the kernel. And we received a different config from
> the build (WRUSS=n).
>
> We diff the two and error out if the built kernel differs from the passed
> configuration. Which is the case here.
I sure hope that diffing script can ignore Kconfig items. Because this
doesn't sound like a reason to "fix" the upstream kernel and as Masahiro
says, it doesn't change anything anyway.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists