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-merge

Re: [Xen-merge] Re: synch_bitops.h

To: xen-merge@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-merge] Re: synch_bitops.h
From: Andi Kleen <ak@xxxxxxx>
Date: Fri, 6 Jan 2006 15:24:07 +0100
Cc: Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Fri, 06 Jan 2006 14:30:46 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060106140512.GD10634@xxxxxxxxxxxx>
List-help: <mailto:xen-merge-request@lists.xensource.com?subject=help>
List-id: xen-merge <xen-merge.lists.xensource.com>
List-post: <mailto:xen-merge@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-merge>, <mailto:xen-merge-request@lists.xensource.com?subject=unsubscribe>
References: <43BE6271.76F0.0078.0@xxxxxxxxxx> <20060106140512.GD10634@xxxxxxxxxxxx>
Sender: xen-merge-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
On Friday 06 January 2006 15:05, Christian Limpach wrote:
> On Fri, Jan 06, 2006 at 12:28:33PM +0100, Jan Beulich wrote:
> > I realize that it was your preference to not split the i386 and x86-64
> > variants, as I had suggested with my patch. However, in course of
> > undoing that patch the bug fixes got dropped, too. Was that
> > intentional?
>
> I dropped the changes where instead of using =m, you suggested using +m.
> The original Linux' bitops.h uses =m and using +m doesn't really make
> a difference in this case.

It's actually using +m in the post 2.6.15 queue.

-Andi

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

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