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] qemu/block-vvfat.c: fix warnings with _FORTIFY_S

To: Olaf Hering <olaf@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] qemu/block-vvfat.c: fix warnings with _FORTIFY_SOURCE
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Wed, 3 Nov 2010 16:54:16 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 03 Nov 2010 09:55:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101103140412.GA10432@xxxxxxxxx>
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>
References: <20101102223841.GA3932@xxxxxxxxx> <19665.23218.700424.328858@xxxxxxxxxxxxxxxxxxxxxxxx> <20101103140412.GA10432@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Olaf Hering writes ("Re: [Xen-devel] [PATCH] qemu/block-vvfat.c: fix warnings 
with _FORTIFY_SOURCE"):
> On Wed, Nov 03, Ian Jackson wrote:
> > However: have you checked whether these problems exist in qemu
> > upstream ?  With Anthony's work on upstreaming Xen support in qemu
> > coming along well, we should be thinking about sending fixes like this
> > upstream.
> 
> The vvfat patch is already upstream, the other one should be there too.
> But I havent verified it, the website does not resolve for me right now.

Great, thanks.  I guess in this case if it gets dropped the compiler
will tell us in due course.

Ian.

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

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