stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: gregkh@linuxfoundation.org
Cc: colin.king@canonical.com, james.l.morris@oracle.com,
	serge@hallyn.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 09:04:06 -0500	[thread overview]
Message-ID: <20171024140406.GA30067@mail.hallyn.com> (raw)

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.

thanks,
serge

             reply	other threads:[~2017-10-24 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 14:04 Serge E. Hallyn [this message]
2017-10-24 19:43 ` FAILED: patch "[PATCH] commoncap: move assignment of fs_ns to avoid null pointer" failed to apply to 4.13-stable tree Greg KH
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=20171024140406.GA30067@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc="In-Reply-To:150883091712759"@kroah.com \
    --cc=colin.king@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.l.morris@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).