rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Timo Grautstück" <timo.grautstueck@web.de>
To: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Cc: "Timo Grautstück" <timo.grautstueck@web.de>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Timo Grautstück" <timo.grautsautstueck@web.de>
Subject: [PATCH v2] lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW
Date: Fri,  4 Oct 2024 10:55:33 +0200	[thread overview]
Message-ID: <20241004085534.14407-1-timo.grautstueck@web.de> (raw)
In-Reply-To: <CANiq72kxOEt2Kb_rxY0+WD6uu=NXy+6PGMvGjTHfNFVXucgH7w@mail.gmail.com>

Just a grammar fix in lib/Kconfig.debug, under the config option RUST_BUILD_ASSERT_ALLOW.

Reported-by: Miguel Ojeda <ojeda@kernel.org>
Closes: https://github.com/Rust-for-Linux/linux/issues/1006
Fixes: ecaa6ddff2fd ("rust: add `build_error` crate")
Signed-off-by: Timo Grautstück <timo.grautsautstueck@web.de>
---
 lib/Kconfig.debug | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 7315f643817a..7312ae7c3cc5 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -3060,7 +3060,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 the 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.44.0


  reply	other threads:[~2024-10-04  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 16:12 [PATCH] lib/Kconfig.debug: fix grammar in RUST_BUILD_ASSERT_ALLOW timo.gr
2023-06-16  1:17 ` Miguel Ojeda
2023-06-25 10:05   ` Timo Grautstück
2023-08-02 15:29     ` Miguel Ojeda
2024-10-04  8:55       ` Timo Grautstück [this message]
2024-10-05 19:13         ` [PATCH v2] " Miguel Ojeda
2024-10-06 14:02           ` [PATCH v3] " Timo Grautstück
2024-10-07 17:14             ` 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=20241004085534.14407-1-timo.grautstueck@web.de \
    --to=timo.grautstueck@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=timo.grautsautstueck@web.de \
    /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).