From: Huw Davies <huw@codeweavers.com>
To: Paul Moore <pmoore@redhat.com>
Cc: netdev@vger.kernel.org, linux-security-module@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH v2 00/18] CALIPSO Implementation
Date: Thu, 11 Feb 2016 14:57:59 +0000 [thread overview]
Message-ID: <20160211145759.GC31695@merlot> (raw)
In-Reply-To: <2084590.x0rrIneakS@sifl>
On Sun, Feb 07, 2016 at 02:56:18PM -0500, Paul Moore wrote:
> Thanks for fixing this patchset up and sending out a v2. I took a closer look
> and just sent out my comments, let me know if you have any questions.
>
> Once we get to a v3 patchset, I think it's time to reach out Oracle and try
> some interop with Solaris TX. Let me know when you are ready and I'll put
> everybody in touch to try to get some testing going.
Thanks for your comments, Paul. I've replied to a couple of them with
answers. For all of others, assume that I have incorporated those
suggestions. I should get v3 out sometime next week.
Thanks again,
Huw.
prev parent reply other threads:[~2016-02-11 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 9:52 [RFC PATCH v2 00/18] CALIPSO Implementation Huw Davies
2016-02-07 19:56 ` Paul Moore
2016-02-11 14:57 ` Huw Davies [this message]
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=20160211145759.GC31695@merlot \
--to=huw@codeweavers.com \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pmoore@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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).