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] blkif.h in sparse tree

To: Gary Pennington <gary.pennington@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] blkif.h in sparse tree
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 19 Feb 2008 10:42:15 +0000
Delivery-date: Tue, 19 Feb 2008 02:42:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080219100505.GA14875@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Achy5BdaVa53aN7XEdysCwAX8io7RQ==
Thread-topic: [Xen-devel] blkif.h in sparse tree
User-agent: Microsoft-Entourage/
On 19/2/08 10:05, "Gary Pennington" <Gary.Pennington@xxxxxxx> wrote:

> I'm puzzled as to why:
> linux-2.6-xen-sparse/include/xen/blkif.h
> includes functionality which looks as though it should be common to all
> OS implementations.

It's just glue, and uses gcc-specific pragmas which are not portable across
compilers. We could stick a BSD license string at the top of the header.

 -- Keir

Xen-devel mailing list

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