[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAQLttPD=Ae==e0CYeQtS78=o_JZFK+zxa29JnUYio52Ug@mail.gmail.com>
Date: Sun, 5 Mar 2023 17:10:08 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Nick Alcock <nick.alcock@...cle.com>
Cc: mcgrof@...nel.org, linux-modules@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org,
arnd@...db.de, akpm@...ux-foundation.org, eugene.loh@...cle.com,
kris.van.hees@...cle.com,
Victor Erminpour <victor.erminpour@...cle.com>
Subject: Re: [PATCH v10 02/13] kbuild: bring back tristate.conf
On Tue, Dec 6, 2022 at 1:32 AM Nick Alcock <nick.alcock@...cle.com> wrote:
>
> tristate.conf was dropped because it is not needed to build
> modules.builtin any more, and doing so avoids one round of recursion
> through the build tree to build it. But it has one property that can be
> obtained in no other way in the current tree: it provides a
> machine-readable record of whether a module is tristate or not.
> (modules.builtin.objs, just added, uses modinfo, which is recorded in
> the source files themselves, but it is Kconfig that actually controls
> whether something can be built as a module.)
>
> So bring it back for this purpose. (Thanks to the refactoring in
> the 5.16 timeframe, this is basically a reimplementation of commit
> 8b41fc4454e36fbfdbb23f940d023d4dece2de29 rather than a simple
> reversion.)
>
> A verifier that uses it will be added in the next commit.
>
> Signed-off-by: Nick Alcock <nick.alcock@...cle.com>
> Reviewed-by: Victor Erminpour <victor.erminpour@...cle.com>
> Reviewed-by: Kris Van Hees <kris.van.hees@...cle.com>
IIRC, I said please do not do this.
Please do not come back with this again.
NACK.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists