From: Fan Wu <wufan@kernel.org>
To: linux-security-module@vger.kernel.org
Subject: [PATCH 1/6] ipe: constify token_default()
Date: Fri, 2 Oct 2026 19:51:30 -0700 [thread overview]
Message-ID: <20261003025135.3666767-2-wufan@kernel.org> (raw)
In-Reply-To: <20261003025135.3666767-1-wufan@kernel.org>
token_default() does not modify its argument, so make it const.
Assisted-by: LLM
Signed-off-by: Fan Wu <wufan@kernel.org>
---
security/ipe/policy_parser.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/ipe/policy_parser.c b/security/ipe/policy_parser.c
index 6fa5bebf8471..f1c05e53667f 100644
--- a/security/ipe/policy_parser.c
+++ b/security/ipe/policy_parser.c
@@ -201,7 +201,7 @@ static int parse_header(char *line, struct ipe_parsed_policy *p)
* * %false - The token is not "DEFAULT"
* * %true - The token is "DEFAULT"
*/
-static bool token_default(char *token)
+static bool token_default(const char *token)
{
return !strcmp(token, "DEFAULT");
}
--
2.55.0
next prev parent reply other threads:[~2026-10-03 2:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 2:51 [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
2026-10-03 2:51 ` Fan Wu [this message]
2026-10-03 2:56 ` [PATCH 1/6] ipe: constify token_default() sashiko-bot
2026-10-03 2:51 ` [PATCH 2/6] ipe: use designated initializers for audit name tables Fan Wu
2026-10-03 2:59 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 3/6] ipe: check parser token table sizes Fan Wu
2026-10-03 2:56 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 4/6] ipe: correct policy text ownership comment Fan Wu
2026-10-03 2:57 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 5/6] ipe: fix enforcement audit Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-03 2:51 ` [PATCH 6/6] ipe: update the project and test suite links Fan Wu
2026-10-03 2:55 ` sashiko-bot
2026-10-06 16:59 ` [PATCH 0/6] ipe: cleanups, an audit fix and updated links Fan Wu
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=20261003025135.3666767-2-wufan@kernel.org \
--to=wufan@kernel.org \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.