All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: James Morris <james.l.morris@oracle.com>,
	linux-security-module@vger.kernel.org
Cc: linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: Security subsystem tree merge to v4.15-rc3
Date: Mon, 11 Dec 2017 16:55:33 -0500	[thread overview]
Message-ID: <1513029333.3530.24.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1712111702560.20676@localhost>

On Mon, 2017-12-11 at 17:05 +1100, James Morris wrote:
> For developers working against the security subsystem tree,
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
> 
> this is now merged to Linus' v4.15-rc3.

Thanks, James!

Mimi

WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: Security subsystem tree merge to v4.15-rc3
Date: Mon, 11 Dec 2017 16:55:33 -0500	[thread overview]
Message-ID: <1513029333.3530.24.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1712111702560.20676@localhost>

On Mon, 2017-12-11 at 17:05 +1100, James Morris wrote:
> For developers working against the security subsystem tree,
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
> 
> this is now merged to Linus' v4.15-rc3.

Thanks, James!

Mimi

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-12-11 21:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11  6:05 Security subsystem tree merge to v4.15-rc3 James Morris
2017-12-11 21:55 ` Mimi Zohar [this message]
2017-12-11 21:55   ` Mimi Zohar
2017-12-18 19:28 ` Casey Schaufler
2017-12-19 20:34   ` James Morris

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=1513029333.3530.24.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=james.l.morris@oracle.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@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.