From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: + stupid-hack-to-make-mainline-build.patch added to -mm tree Date: Wed, 07 Mar 2007 10:28:28 -0800 Message-ID: <45EF044C.2080307@goop.org> References: <45EDD82F.90204@vmware.com> <1173225182.24738.507.camel@localhost.localdomain> <45EE0628.1080108@goop.org> <45EE08E8.2020008@vmware.com> <1173228544.24738.514.camel@localhost.localdomain> <45EE0D10.7070807@vmware.com> <1173230305.24738.529.camel@localhost.localdomain> <45EE1EA3.90803@vmware.com> <1173256666.24738.576.camel@localhost.localdomain> <45EEF966.6060902@goop.org> <20070307175232.GB31371@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070307175232.GB31371@elte.hu> Sender: linux-kernel-owner@vger.kernel.org To: Ingo Molnar Cc: tglx@linutronix.de, Dan Hecht , Zachary Amsden , akpm@linux-foundation.org, ak@suse.de, Virtualization Mailing List , Rusty Russell , LKML , john stultz List-Id: virtualization@lists.linuxfoundation.org Ingo Molnar wrote: > /For you/ it's certainly no big deal, you dont have to fix it up and you > dont have to keep it flexible ;) > How flexible does it need to be? Its a simple time source and event driver. How flexible does the pit driver need to be? It's just a small leaf node hanging off a large existing piece of kernel infrastructure. > and really, i'm not expecting miracles, i've never seen any hardware > vendor argue /against/ support for their own hardware =B-) > And since when has it been kernel policy to argue against including a well written, self-contained, vendor-provided driver for a piece of hardware? J