From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <john.johansen@canonical.com>, <paul@paul-moore.com>,
<jmorris@namei.org>, <serge@hallyn.com>, <ruanjinjie@huawei.com>,
<apparmor@lists.ubuntu.com>,
<linux-security-module@vger.kernel.org>
Subject: [PATCH -next] apparmor: Remove unused parameter L1 in macro next_comb
Date: Mon, 2 Sep 2024 15:39:04 +0800 [thread overview]
Message-ID: <20240902073904.3520301-1-ruanjinjie@huawei.com> (raw)
In the macro definition of next_comb(), a parameter L1 is accepted,
but it is not used. Hence, it should be removed.
Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
---
security/apparmor/include/label.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/security/apparmor/include/label.h b/security/apparmor/include/label.h
index 2a72e6b17d68..2635eef0ae2b 100644
--- a/security/apparmor/include/label.h
+++ b/security/apparmor/include/label.h
@@ -160,7 +160,7 @@ int aa_label_next_confined(struct aa_label *l, int i);
#define label_for_each_cont(I, L, P) \
for (++((I).i); ((P) = (L)->vec[(I).i]); ++((I).i))
-#define next_comb(I, L1, L2) \
+#define next_comb(I, L2) \
do { \
(I).j++; \
if ((I).j >= (L2)->size) { \
@@ -174,7 +174,7 @@ do { \
#define label_for_each_comb(I, L1, L2, P1, P2) \
for ((I).i = (I).j = 0; \
((P1) = (L1)->vec[(I).i]) && ((P2) = (L2)->vec[(I).j]); \
- (I) = next_comb(I, L1, L2))
+ (I) = next_comb(I, L2))
#define fn_for_each_comb(L1, L2, P1, P2, FN) \
({ \
--
2.34.1
next reply other threads:[~2024-09-02 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 7:39 Jinjie Ruan [this message]
2024-11-09 20:39 ` [PATCH -next] apparmor: Remove unused parameter L1 in macro next_comb John Johansen
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=20240902073904.3520301-1-ruanjinjie@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=apparmor@lists.ubuntu.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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).