Linux Security Modules development
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Kees Cook <keescook@chromium.org>,
	linux-kernel@vger.kernel.org,
	"Serge E. Hallyn" <serge@hallyn.com>,
	Casey Schaufler <casey@schaufler-ca.com>,
	KP Singh <kpsingh@chromium.org>,
	linux-security-module@vger.kernel.org,
	kernel test robot <lkp@intel.com>,
	linux-hardening@vger.kernel.org
Subject: Re: [PATCH] LSM: Avoid warnings about potentially unused hook variables
Date: Thu, 14 Oct 2021 08:51:54 +1100 (AEDT)	[thread overview]
Message-ID: <f1a143f5-7972-413d-497c-617b915c4b30@namei.org> (raw)
In-Reply-To: <CAHC9VhT0+omwDjqrJ2BtnRfa8SSGAkyUvB6WX95E=ntf9gUbmQ@mail.gmail.com>

On Wed, 13 Oct 2021, Paul Moore wrote:

> Looks reasonable to me, thanks Kees.  Unless James wants to pick this
> up for the security tree, I can pull this into the SElinux tree with
> the io_uring change which is causing the testing robot to complain.
> 
> Acked-by: Paul Moore <paul@paul-moore.com>

Sounds good.


Acked-by: James Morris <jamorris@linux.microsoft.com>


-- 
James Morris
<jmorris@namei.org>


  reply	other threads:[~2021-10-13 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 17:28 [PATCH] LSM: Avoid warnings about potentially unused hook variables Kees Cook
2021-10-13 17:53 ` Paul Moore
2021-10-13 21:51   ` James Morris [this message]
2021-10-14 20:10     ` Paul Moore

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=f1a143f5-7972-413d-497c-617b915c4b30@namei.org \
    --to=jmorris@namei.org \
    --cc=casey@schaufler-ca.com \
    --cc=keescook@chromium.org \
    --cc=kpsingh@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lkp@intel.com \
    --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