From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 00/10] Various virt requirements
Date: Tue, 30 Oct 2012 14:18:23 -0400 [thread overview]
Message-ID: <509019EF.7020308@tresys.com> (raw)
In-Reply-To: <1350822019-15079-1-git-send-email-dominick.grift@gmail.com>
On 10/21/12 08:20, Dominick Grift wrote:
> These are required by the virt module
>
> Dominick Grift (10):
> For svirt_lxc_domain
> For svirt_lxc_domain
> For svirt_lxc_domain
> For virtd lxc
> For virtd_lxc
> For virtd_lxc
> For virtd lxc
> For virtd lxc
> For virtd
> For virtd
>
> policy/modules/kernel/devices.if | 18 +++++++++++
> policy/modules/kernel/files.if | 57 ++++++++++++++++++++++++++++++++++-
> policy/modules/kernel/filesystem.if | 36 ++++++++++++++++++++++
> policy/modules/kernel/terminal.if | 19 +++++++++++
> policy/modules/system/clock.if | 19 +++++++++++
> policy/modules/system/sysnetwork.if | 19 +++++++++++
> policy/modules/system/udev.if | 19 +++++++++++
> 7 files changed, 186 insertions(+), 1 deletions(-)
1-9 merged, I never received 10.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-10-30 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 12:20 [refpolicy] [PATCH 00/10] Various virt requirements Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 01/10] For svirt_lxc_domain Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 02/10] " Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 03/10] " Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 04/10] For virtd lxc Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 05/10] For virtd_lxc Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 06/10] " Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 07/10] For virtd lxc Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 08/10] " Dominick Grift
2012-10-21 12:20 ` [refpolicy] [PATCH 09/10] For virtd Dominick Grift
2012-10-30 18:18 ` Christopher J. PeBenito [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=509019EF.7020308@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.