Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 19 Oct 2018 11:21:25 +1100 (AEDT)
From:   James Morris <jmorris@namei.org>
To:     Kees Cook <keescook@chromium.org>
cc:     linux-kernel@vger.kernel.org,
        Casey Schaufler <casey@schaufler-ca.com>,
        John Johansen <john.johansen@canonical.com>,
        linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] loadpin updates for security-next
In-Reply-To: <20181018230542.GA48284@beast>
Message-ID: <alpine.LRH.2.21.1810191121050.29701@namei.org>
References: <20181018230542.GA48284@beast>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 18 Oct 2018, Kees Cook wrote:

> Hi James,
> 
> Please pull these loadpin changes for security-next. This is a small
> reporting improvement and the param change needed for the ordering
> series (but since the loadpin change is desired and separable, I'm
> putting it here).
> 
> Thanks!
> 
> -Kees
> 
> The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
> 
>   Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/loadpin-security-next
> 

Thanks, pulled to next-loadpin and next-testing.

-- 
James Morris
<jmorris@namei.org>