# Re: \[PATCH v10 02/13\] kbuild: bring back tristate.conf

- From: Masahiro Yamada \<masahiroy@kernel.org\>
- Date: 2023-03-05 08:10:53 
- List: linux-modules
- Page: https://ratatoskr.run/linux-modules/2023/03/2120465
- Thread: https://ratatoskr.run/linux-modules/2022/12/2030624/t.md

```text
On Tue, Dec 6, 2022 at 1:32 AM Nick Alcock [ref] 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 <redacted>
> Reviewed-by: Victor Erminpour <redacted>
> Reviewed-by: Kris Van Hees <redacted>



IIRC, I said please do not do this.
Please do not come back with this again.

NACK.






--
Best Regards
Masahiro Yamada
```