[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <boris.20231109093619@codesynthesis.com>
Date: Thu, 9 Nov 2023 09:43:44 +0200
From: Boris Kolpackov <boris@...esynthesis.com>
To: Matthew Maurer <mmaurer@...gle.com>
Cc: Masahiro Yamada <masahiroy@...nel.org>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
linux-kbuild@...r.kernel.org, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>,
Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>,
linux-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH 2/3] kconfig: Add special rust_modules config option
Matthew Maurer <mmaurer@...gle.com> writes:
> Adds support for the rust_modules kconfig type, which works similarly to
> modules, but for restricting or allowing the use of modules which
> directly depend on Rust.
>
> [...]
>
> +struct symbol *modules_rust_sym;
> +static tristate modules_rust_val;
> +
> +bool sym_depends_rust(struct symbol *sym)
> +{
> + static struct symbol *rust_sym;
> +
> + if (!rust_sym)
> + rust_sym = sym_find("RUST");
> + return expr_depends_symbol(sym->dir_dep.expr, rust_sym, true);
> +}
> +
Hm, this feels like a quick and dirty hack to me: will we be hardcoding
a symbol for each language?
I know there is little sympathy for other projects that use Kconfig,
and whatever Linux needs, goes, but still, this feels like a step too
far.
Powered by blists - more mailing lists