[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] linux/arch/xen/i386 or linux/arch/i386/xen

> OK, how about one step at a time.  It's already a huge step to move
> things around (between Kconfig, and tangled source, and headers...).
> The advantage of move towards a known target (sub-arch) is there's
> infrastructure in place to support it already.  I don't think it's a
> dead-end to go there and then look towards the issues you brought up.

It's OK with me.  Sometimes two-step changes are better than one.
It would be nice to have finished the second step before Xen support
finds its way into the mainstream kernel though (IMHO).

> > And since this will appear hard-coded in include lines
> > in source files, we do need to decide one way or the
> > other.
> Things move all the time, it's just a simple matter of patching ;-)
> Or did I misunderstand you?

Yeah, I was just trying to pre-answer the question:  "Does this
silly naming issue really matter?"  with, yes, a fair number of
files will have to change.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.