[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 9 Sep 2020 13:14:00 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Arnaud Lacombe <lacombar@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
linux-kernel@...r.kernel.org,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Tony Luck <tony.luck@...el.com>
Subject: Re: [PATCH v1] x86/defconfigs: Unbreak 32-bit defconfig builds
On Wed, Sep 09, 2020 at 10:00:20AM +0200, Ingo Molnar wrote:
> * Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> > On Tue, Sep 08, 2020 at 02:13:54PM +0200, Ingo Molnar wrote:
> > > * Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
...
> > uname => x86_64
> > make i386_defconfig
> >
> > It was very convenient to not supply ARCH when build on multi-arch host.
>
> Nice, TIL about the extended 'make *config' targets. :-)
>
> Curiously, they aren't even mentioned in the 'configuration targets'
> section of 'make help' and are not discoverable unless you know their
> locations.
>
> Anyway, your fix makes sense now to me too.
I see you applied original patch from Daniel.
> Do we need a similar for x86_64 defconfig, when built on 32-bit hosts? (not
> that anyone does that in practice, but just for completeness.)
I never heard about such use, I consider it more academic rather than
practical.
> Also, it would be nice if there was a way to annotate the defconfig for
> 'make savedefconfig' preserved these ARCH choices - it currently strips out
> all non-enabled options that match their default configuration value.
Hmm... Yes, perhaps it would be nice to have such an exception.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists