| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] MAJOR cleanup in patched-from-linux code
I forgot to add... a clean clone is suggested as many
of the patched files changed and some confusion results
from building on top of a bk pull.
> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf
> Of Magenheimer, Dan (HP Labs Fort Collins)
> Sent: Monday, May 02, 2005 2:32 PM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] MAJOR cleanup in patched-from-linux code
>
> I just checked in to xen-ia64.bkbits.net://xeno-unstable-ia64.bk
> a major cleanup to the linux patch files. Many of the patches
> were cluttered with unnecessary additions and some of the files
> appeared to be better off checked in directly rather than on top
> of the linux source.
>
> (Note that bkbits.net is having some problems in its admin
> interface, so it may take a day or two to push these changes
> to xen.bkbits.net.)
>
> Here's the results:
>
> BEFORE:
> 38 patch files
> 1027 lines added
> 160 lines subtracted
>
> AFTER:
> 24 patch files
> 348 lines added
> 2 lines subtracted
>
> Of the 348 lines added, 151 are real code and the rest
> are conditional compile directives (#ifdef/#else/#endif etc).
> All changes are clearly marked with ifdef's, with the
> exception of two lines which are in the middle of a huge
> assembly macro.
>
> Why not get rid of these entirely and just check in the
> Linux sources? Because mkbuildtree links in almost 32000
> lines of Linux/ia64 source files and only slightly more
> than 1% change is required to utilize these in Xen/ia64.
> That's leverage!
>
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home