[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <PAXP190MB1631B7C90A99FCEBB1594AAE8B4DA@PAXP190MB1631.EURP190.PROD.OUTLOOK.COM>
Date: Mon, 5 Jun 2023 18:12:23 +0200
From: timo.gr@...mail.de
To: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Timgrau <timo.gr@...mail.de>, Miguel Ojeda <ojeda@...nel.org>
Subject: [PATCH] lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW
From: Timgrau <timo.gr@...mail.de>
Just a grammar fix in lib/Kconfig.debug, under the config option RUST_BUILD_ASSERT_ALLOW.
Signed-off-by: Timgrau <timo.gr@...mail.de>
Suggested-by: Miguel Ojeda <ojeda@...nel.org>
Link: https://github.com/Rust-for-Linux/linux/issues/1006#issue-1696318406
Closes: https://github.com/Rust-for-Linux/linux/issues/1006#issue-1696318406
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ce51d4dc6803..a56b9b368e78 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -2899,7 +2899,7 @@ config RUST_BUILD_ASSERT_ALLOW
bool "Allow unoptimized build-time assertions"
depends on RUST
help
- Controls how are `build_error!` and `build_assert!` handled during build.
+ Controls how `build_error!` and `build_assert!` are handled during build.
If calls to them exist in the binary, it may indicate a violated invariant
or that the optimizer failed to verify the invariant during compilation.
--
2.40.1
Powered by blists - more mailing lists