Re: [Xen-devel] incompatible prototypes

To:	PUCCETTI Armand <armand.puccetti@xxxxxx>
Subject:	Re: [Xen-devel] incompatible prototypes
From:	Keir Fraser <keir@xxxxxxxxxxxxx>
Date:	Fri, 27 Apr 2007 17:09:05 +0100
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 27 Apr 2007 09:07:50 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<46321BFC.9090804@xxxxxx>
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:	AceI5mC5n5ECCPTZEduDOgAX8io7RQ==
Thread-topic:	[Xen-devel] incompatible prototypes
User-agent:	Microsoft-Entourage/11.3.3.061214

On 27/4/07 16:51, "PUCCETTI Armand" <armand.puccetti@xxxxxx> wrote:

> You're quite right on the first point. However the incompatible prototypes
> might lead to errors if some of these functions are called.

__attribute__((regparm(0))) is the default for i386 anyway. Really
asmlinkage should define to nothing for all x86 architectures, and we can
just kill off all use of asmlinkage under arch/x86.

 -- Keir

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

Previous by Date:	Re: [Xen-devel] incompatible prototypes, PUCCETTI Armand
Next by Date:	Re: [Xen-devel] incompatible prototypes, Jeremy Fitzhardinge
Previous by Thread:	Re: [Xen-devel] incompatible prototypes, PUCCETTI Armand
Next by Thread:	Re: [Xen-devel] incompatible prototypes, Jeremy Fitzhardinge
Indexes:	[Date] [Thread] [Top] [All Lists]

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] incompatible prototypes