[Xen-devel] Re: [Xen-ia64-devel] [Patch] [RESEND] cleanup warning in xen/ia64

[Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>]

Hi,

We changed from "#if 0" to "#ifndef XEN" in "cleanup.linux-xen.patch",
and updated "cleanup.xen.patch" to changeset:9000.
We don't resend "cleanup.include.xen.patch", because it was committed 
to xen-unstable tree.

Signed-off-by: Tsunehisa Doi <doi.tsunehisa@xxxxxxxxxxxxxx>
Signed-off-by: Kouya SHIMURA <kouya@xxxxxxxxxxxxxx>
Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Signed-off-by: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>

Best regards,
 Kan, and Fujitsu team

Alex Williamson wrote:
>On Mon, 2006-02-27 at 10:48 +0900, Akio Takebe wrote:
>> Hi, all
>> 
>> We clean up warning in xen/ia64 .
>> We have cleaned up many warnings, but it remainded some warnings yet.
>> 
>> These patches fix many issue (ex. panic dom0, oops domU/dom0...).
>> we will fix compile warnnings one step at a time. 
>> 
>> For xen (common)
>>  - cleanup.include.xen.patch
>> 
>> For xen (ia64)
>>  - cleanup.include.asm-ia64.patch
>>  - cleanup.linux.patch
>>  - cleanup.linux-xen.patch
>>  - cleanup.xen.patch
>
>  This looks really good.  A minor comment; I see lots of "#if 0" blocks
>added to the linux-xen files.  These need to be "#ifndef XEN" so that we
>can more easily manage these changes versus upstream linux.  If nobody
>else has comments, I can fix those when it gets committed to the tree.
>thanks,
>
>       Alex
>
>-- 
>Alex Williamson                             HP Linux & Open Source Lab
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel
>

cleanup.include.asm-ia64.patch
Description: Binary data

cleanup.linux-xen.patch
Description: Binary data

cleanup.linux.patch
Description: Binary data

cleanup.xen.patch
Description: Binary data

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