This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCHv2] libxl: Exposed Flask XSM functionality

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCHv2] libxl: Exposed Flask XSM functionality
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Mon, 11 Apr 2011 15:19:30 +0100
Cc: Machon Gregory <mbgrego@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 Apr 2011 07:20:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19875.3239.712293.898010@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4D99D57E.9020501@xxxxxxxxxxxxxx> <19875.3239.712293.898010@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2011-04-11 at 15:13 +0100, Ian Jackson wrote:
> Machon Gregory writes ("[Xen-devel] [PATCHv2] libxl: Exposed Flask XSM 
> functionality"):
> > Adds support for assigning a label to domains, obtaining and setting the
> > current enforcing mode, and loading a policy with xl command when the
> > Flask XSM is in use.
> Thanks for this.  I would like to apply this patch but I don't seem to
> be able to find the corresponding libxc patch which is obviously
> necessary as a part of this series.
> Very likely I have dropped it and now aren't using the right search
> terms, so perhaps you could repost it for me ?
> While I'm here can I suggest that you use software which posts a
> series of patches as a single thread rather than as a separate thread
> for each patch ?  git-send-email knows how to do this; I don't know
> how to get hg to do it but no doubt someone here does.

I think it's the default if you give the "hg email" command a range
spanning > 1 commit.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>