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;
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.21.1801291040280.29680@namei.org>
References: <alpine.LRH.2.21.1801291040280.29680@namei.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Wed, 31 Jan 2018 13:21:44 -0800
Message-ID: <CA+55aFw1vWWmv5Ebq9yWVDFm4SQUG_fNd3f5yoYkWRTfUNaL_Q@mail.gmail.com>
Subject: Re: [GIT PULL] Security subsystem updates for v4.16
To:     James Morris <jmorris@namei.org>, Kees Cook <keescook@chromium.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        LSM List <linux-security-module@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sun, Jan 28, 2018 at 3:41 PM, James Morris <jmorris@namei.org> wrote:
>
> Note that individual trees may also be pulled via:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
>         next-integrity
>         next-smack
>         next-tpm

So I did that, because it makes it easier and more controlled for me.
But then when double-checking that the end result is identical to your
full pull request, I end up missing the seccomp tree.

I can pull that separately too, but it was missing explanations and a
real pull request, so I left it alone.

           Linus