From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] linux-integrity patches for 4.15-security-next-testing
Date: Thu, 9 Nov 2017 12:23:37 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711091221160.20834@localhost> (raw)
In-Reply-To: <1510184012.4484.69.camel@linux.vnet.ibm.com>
On Wed, 8 Nov 2017, Mimi Zohar wrote:
> > Merged to next-testing and next-integrity in
> > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
>
> Hm, does this mean that these patches will be included in your pull
> request? ?Based on Linus "comments" last time, is this such a good
> idea?
I may send him next-testing, with everything applied, and also links to
the appropriate subsystem branches so he can pull them independently. I
haven't decided yet (vs. sending a bunch of separate pull requests).
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-11-09 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 21:54 [GIT PULL] linux-integrity patches for 4.15-security-next-testing Mimi Zohar
2017-11-08 23:18 ` James Morris
2017-11-08 23:33 ` Mimi Zohar
2017-11-09 1:23 ` James Morris [this message]
2017-11-09 3:08 ` Mimi Zohar
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=alpine.LFD.2.20.1711091221160.20834@localhost \
--to=james.l.morris@oracle.com \
--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.