WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0/2] PV framebuffer

To: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/2] PV framebuffer
From: Markus Armbruster <armbru@xxxxxxxxxx>
Date: Thu, 16 Nov 2006 12:46:21 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 16 Nov 2006 03:48:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200611161031.kAGAVxKK023149@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> (Atsushi SAKAI's message of "Thu, 16 Nov 2006 19:31:10 +0900")
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>
References: <87odrfptrb.fsf@xxxxxxxxxxxxxxxxx> <200611160109.kAG19CiO003967@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <87velfhkdl.fsf@xxxxxxxxxxxxxxxxx> <200611161031.kAGAVxKK023149@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx> writes:

> Hi, Markus
>
> your code location of xenfb.h is in 
> linux-2.6.16.29-xen/include/xen/interface/io/xenfb.h
> it is wrong position.
>
> It should be located in 
> xen/include/public/io

If my patch were relative to the Xen source tree, you'd be right.  It
isn't.  There is no xen directory in a Linux source tree.

Yes, that means you can't apply my patch directly to your Xen source
tree.  Sorry about that.  I explained my reasons.

[...]

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel