From: Paul Moore <paul@paul-moore.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] lsm: remove LSM_COUNT and LSM_CONFIG_COUNT
Date: Mon, 26 Aug 2024 19:12:17 -0400 [thread overview]
Message-ID: <024d26e3590a84ee81fe66050aae52dc@paul-moore.com> (raw)
In-Reply-To: <5089fc1c-0172-4ccf-9ad1-28ff1b649597@I-love.SAKURA.ne.jp>
On Aug 25, 2024 Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> wrote:
>
> Because these are equals to MAX_LSM_COUNT. Also, we can avoid dynamic
> memory allocation for ordered_lsms because MAX_LSM_COUNT is a constant.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
> security/security.c | 37 ++++---------------------------------
> 1 file changed, 4 insertions(+), 33 deletions(-)
Looks reasonable to me, merged into lsm/dev, thanks.
--
paul-moore.com
prev parent reply other threads:[~2024-08-26 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 14:05 [PATCH] lsm: remove LSM_COUNT and LSM_CONFIG_COUNT Tetsuo Handa
2024-08-26 23:12 ` Paul Moore [this message]
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=024d26e3590a84ee81fe66050aae52dc@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).