[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090302120445.GA29015@elte.hu>
Date: Mon, 2 Mar 2009 13:04:45 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Gerd Hoffmann <kraxel@...hat.com>
Cc: Jeremy Fitzhardinge <jeremy@...p.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: [PATCH] xen: core dom0 support
* Gerd Hoffmann <kraxel@...hat.com> wrote:
> Ingo Molnar wrote:
> >>> In three years time, will we regret having merged this?
> >> Its a pretty minor amount of extra stuff on top of what's been
> >> added over the last 3 years, so I don't think it's going to
> >> tip the scales on its own. I wouldn't be comfortable in
> >> trying to merge something that's very intrusive.
> >
> > Hm, how can the same code that you call "massive out-of-tree
> > patches which doesn't make anyone happy" in an out of tree
> > context suddenly become non-intrusive "minor amount of extra
> > stuff" in an upstream context?
>
> The current, out-of-tree xen kernel stuff is based on 2.6.18.
> [...]
Sure, but what i'm pointing out is the following aspect of
communication:
>>> [...] At the moment its all running on massive out-of-tree
>>> patches, which doesn't make anyone happy. It's best that it
>>> be in the mainline kernel. You know, like we argue for
>>> everything else.
Comparing it to a 2.6.18 base is simply misleading when it comes
to upstreaming something. Enterprise distros will rebase, and
their out-of-tree pile of patches will shrink.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists