From: Paul Moore <paul@paul-moore.com>
To: Yue Haibing <yuehaibing@huawei.com>, <jmorris@namei.org>,
<serge@hallyn.com>, <kees@kernel.org>, <casey@schaufler-ca.com>
Cc: <linux-security-module@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <yuehaibing@huawei.com>
Subject: Re: [PATCH] lockdown: Make lockdown_lsmid static
Date: Thu, 15 Aug 2024 12:11:40 -0400 [thread overview]
Message-ID: <bfc25c139caf8eacc02973b94ac05030@paul-moore.com> (raw)
In-Reply-To: <20240814033004.2216000-1-yuehaibing@huawei.com>
On Aug 13, 2024 Yue Haibing <yuehaibing@huawei.com> wrote:
>
> Fix sparse warning:
>
> security/lockdown/lockdown.c:79:21: warning:
> symbol 'lockdown_lsmid' was not declared. Should it be static?
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> Reviewed-by: Kees Cook <kees@kernel.org>
> ---
> security/lockdown/lockdown.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Merged into lsm/dev, thanks!
--
paul-moore.com
prev parent reply other threads:[~2024-08-15 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 3:30 [PATCH -next] lockdown: Make lockdown_lsmid static Yue Haibing
2024-08-15 16:01 ` Kees Cook
2024-08-15 16:11 ` 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=bfc25c139caf8eacc02973b94ac05030@paul-moore.com \
--to=paul@paul-moore.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=yuehaibing@huawei.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