mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 2/2] security: Kconfig.policy: fix typos
Date: Fri,  3 Jul 2026 12:23:44 +0200	[thread overview]
Message-ID: <20260703102344.1957129-2-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20260703102344.1957129-1-u.oelmann@pengutronix.de>

Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
 security/Kconfig.policy | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/security/Kconfig.policy b/security/Kconfig.policy
index 2c8e8399a0ec..d4ca4300504d 100644
--- a/security/Kconfig.policy
+++ b/security/Kconfig.policy
@@ -5,9 +5,9 @@
 menuconfig SECURITY_POLICY
 	bool "Security Policy Support"
 	help
-	  A Security policy is a collection of security configuration options
+	  A security policy is a collection of security configuration options
 	  that can be activated together at runtime.
-	  Together, the describe a security state that barebox should operate in.
+	  Together, they describe a security state that barebox should operate in.
 
 	  Policies can be registered by board code or supplied by
 	  an external build system. The policy name must be unique across
@@ -32,7 +32,7 @@ menuconfig SECURITY_POLICY
 	    lockdown  Factory bring up is done and device is ready for use
 	              in the field with barebox as part of the secure boot
 	              chain. This policy usually disallows booting unsigned
-	              images
+	              images.
 
 	    tamper    Tampering attempt was detected. The security policy would
 	              take steps to protect secrets (up to bricking the device).
-- 
2.47.3




  reply	other threads:[~2026-07-03 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 10:23 [PATCH 1/2] common: Kconfig: fix typo Ulrich Ölmann
2026-07-03 10:23 ` Ulrich Ölmann [this message]
2026-07-07  6:48 ` Sascha Hauer

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=20260703102344.1957129-2-u.oelmann@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=barebox@lists.infradead.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