From: Neal Gompa <neal@gompa.dev>
To: rust-for-linux@vger.kernel.org
Cc: asahi@lists.linux.dev, linux-kernel@vger.kernel.org,
Miguel Ojeda <ojeda@kernel.org>,
Hector Martin <marcan@marcan.st>, Janne Grunau <j@jannau.net>,
Asahi Lina <lina@asahilina.net>
Subject: Re: [PATCH v2] init/Kconfig: Only block on RANDSTRUCT for RUST
Date: Sun, 18 Aug 2024 03:04:17 -0400 [thread overview]
Message-ID: <CAEg-Je9qtud+9uJdratbLmD9EOWPrFh8xn5==-ip_AMZF82Vsw@mail.gmail.com> (raw)
In-Reply-To: <20240731125615.3368813-1-neal@gompa.dev>
On Wed, Jul 31, 2024 at 8:57 AM Neal Gompa <neal@gompa.dev> wrote:
>
> When enabling Rust in the kernel, we only need to block on the
> RANDSTRUCT feature and GCC plugin. The rest of the GCC plugins
> are reasonably safe to enable.
>
> Signed-off-by: Neal Gompa <neal@gompa.dev>
> ---
> Changes in v2
> - Drop changing !RANDSTRUCT to RANDSTRUCT_NONE
> (they're equivalent anyway)
> ---
> init/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/init/Kconfig b/init/Kconfig
> index a465ea9525bd..0939486938cc 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1900,7 +1900,7 @@ config RUST
> depends on RUST_IS_AVAILABLE
> depends on !CFI_CLANG
> depends on !MODVERSIONS
> - depends on !GCC_PLUGINS
> + depends on !GCC_PLUGIN_RANDSTRUCT
> depends on !RANDSTRUCT
> depends on !DEBUG_INFO_BTF || PAHOLE_HAS_LANG_EXCLUDE
> help
> --
> 2.45.2
>
Bump for notice... Can we get this looked at to incorporate for 6.11?
--
真実はいつも一つ!/ Always, there's only one truth!
next prev parent reply other threads:[~2024-08-18 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 12:54 [PATCH v2] init/Kconfig: Only block on RANDSTRUCT for RUST Neal Gompa
2024-08-18 7:04 ` Neal Gompa [this message]
2024-08-18 7:55 ` Miguel Ojeda
2024-08-18 21:32 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEg-Je9qtud+9uJdratbLmD9EOWPrFh8xn5==-ip_AMZF82Vsw@mail.gmail.com' \
--to=neal@gompa.dev \
--cc=asahi@lists.linux.dev \
--cc=j@jannau.net \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).