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: <8b079d9c-f436-eb11-0060-9cad1525aa62@canonical.com>
References: <8b079d9c-f436-eb11-0060-9cad1525aa62@canonical.com>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri, 9 Feb 2018 15:01:55 -0800
Message-ID: <CA+55aFx7fnnV+ECGKxtQB5wwmzS8kqO=UrO1VdwvXMsT=+4nSA@mail.gmail.com>
Subject: Re: [GIT PULL] apparmor updates for v4.16
To:     John Johansen <john.johansen@canonical.com>
Cc:     LKLM <linux-kernel@vger.kernel.org>,
        "open list:SECURITY SUBSYSTEM" 
        <linux-security-module@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Feb 9, 2018 at 12:19 PM, John Johansen
<john.johansen@canonical.com> wrote:
>
> Please pull these apparmor changes for v4.16

No.

You had an extra two weeks because 4.15 was delayed.

Yet you send me a series of patches that have been committed today, on
a Friday before the weekend when the merge window closes.

And none of this appears to have been in linux-next, at least not as
of February 1st, when the merge window opened.

No no no.

This can all wait for 4.17. And if the same problem persists, it can
wait longer.

               Linus