From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Fabian Pflug <f.pflug@pengutronix.de>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] security: policy: remove duplicate SECURITY_POLICY_PATH symbol
Date: Thu, 23 Oct 2025 17:41:59 +0200 [thread overview]
Message-ID: <20251023154202.1877854-1-a.fatoum@pengutronix.de> (raw)
Likely a side effect of rebasing, the symbol SECURITY_POLICY_PATH was
introduced twice:
- First in commit b720fb9a905d ("Add security policy support")
- Then again in commit 79cd2e4fe633
("security: policy: support externally provided configs")
Kconfig can handle this, but it's unintended, so remove a copy.
Fixes: b720fb9a905d ("Add security policy support")
Reported-by: Fabian Pflug <f.pflug@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
security/Kconfig.policy | 15 ---------------
1 file changed, 15 deletions(-)
diff --git a/security/Kconfig.policy b/security/Kconfig.policy
index 1f3becd4fba7..9ea52e91dad3 100644
--- a/security/Kconfig.policy
+++ b/security/Kconfig.policy
@@ -83,21 +83,6 @@ config SECURITY_POLICY_PATH
Absolute paths are disallowed.
-config SECURITY_POLICY_PATH
- string
- depends on SECURITY_POLICY
- prompt "Paths to additional security policies"
- help
- Space separated list of security policies that should be
- compiled into barebox and registered. This option currently
- requires each security policy to match security/*.sconfig, i.e.
- be directly located in the security/ directory of the source
- source tree and have the .sconfig extension.
- If left empty, only security policies explicitly provided
- and registered by board code will be available.
-
- Absolute paths are disallowed.
-
config SECURITY_POLICY_NAMES
bool
--
2.47.3
reply other threads:[~2025-10-23 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251023154202.1877854-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.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