[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45EF044C.2080307@goop.org>
Date: Wed, 07 Mar 2007 10:28:28 -0800
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Ingo Molnar <mingo@...e.hu>
CC: tglx@...utronix.de, Dan Hecht <dhecht@...are.com>,
Zachary Amsden <zach@...are.com>, akpm@...ux-foundation.org,
ak@...e.de,
Virtualization Mailing List <virtualization@...ts.osdl.org>,
Rusty Russell <rusty@...tcorp.com.au>,
LKML <linux-kernel@...r.kernel.org>,
john stultz <johnstul@...ibm.com>
Subject: Re: + stupid-hack-to-make-mainline-build.patch added to -mm tree
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
-
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