From: Greg KH <gregkh@linuxfoundation.org>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: colin.king@canonical.com, james.l.morris@oracle.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] commoncap: move assignment of fs_ns to avoid null pointer" failed to apply to 4.13-stable tree
Date: Tue, 24 Oct 2017 21:43:03 +0200 [thread overview]
Message-ID: <20171024194303.GB6571@kroah.com> (raw)
In-Reply-To: <20171024140406.GA30067@mail.hallyn.com>
On Tue, Oct 24, 2017 at 09:04:06AM -0500, Serge E. Hallyn wrote:
> On Tue, Oct 24, 2017 at 09:41:57AM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.13-stable tree.
>
> yeah it's not relevant because the namespaced file capabilities patch is not
> applied there.
then the fact that it was tagged for stable is a bit odd...
oh well,
greg k-h
next prev parent reply other threads:[~2017-10-24 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 14:04 FAILED: patch "[PATCH] commoncap: move assignment of fs_ns to avoid null pointer" failed to apply to 4.13-stable tree Serge E. Hallyn
2017-10-24 19:43 ` Greg KH [this message]
2017-10-24 20:21 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2017-10-24 7:41 gregkh
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=20171024194303.GB6571@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=james.l.morris@oracle.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.