[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070128212618.GA11547@elte.hu>
Date: Sun, 28 Jan 2007 22:26:18 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Jeff Garzik <jeff@...zik.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Greg Kroah-Hartman <greg@...ah.com>,
Tony Luck <tony.luck@...el.com>,
Grant Grundler <grundler@...isc-linux.org>,
linux-kernel@...r.kernel.org,
Kyle McMartin <kyle@...isc-linux.org>, linuxppc-dev@...abs.org,
Brice Goglin <brice@...i.com>, shaohua.li@...el.com,
linux-pci@...ey.karlin.mff.cuni.cz,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 0/6] MSI portability cleanups
* Eric W. Biederman <ebiederm@...ssion.com> wrote:
> I'm not arguing against an operations based approach. I'm arguing for
> simple obviously correct steps, and not throwing the baby out with the
> bath water.
>
> My patches should be a precursor to an operations based approach
> because they are simple step from where we are now.
yeah. I'd say your approach is to go from A to B:
[A] -----------------------------------------------------> [B]
|
[C]
while there might be some other arguments that "no, lets go to C
instead", i say lets not throw away the already implemented and already
working and nicely layered [A]->[B] transition, just because there's an
argument whether the end result should be 'B' or 'C'. Unless someone who
wants to see 'C' produces a patchset that walks the whole way i dont see
any reason to not go with your patchset. It clearly removes alot of
cruft.
Acked-by: Ingo Molnar <mingo@...e.hu>
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