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 <[email protected]>
Signed-off-by: Ahmad Fatoum <[email protected]>
---
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
