[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070131171812.GD4468@elte.hu>
Date: Wed, 31 Jan 2007 18:18:12 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Daniel Walker <dwalker@...sta.com>
Cc: akpm@...l.org, linux-kernel@...r.kernel.org, johnstul@...ibm.com,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 10/23] clocksource: remove update_callback
* Daniel Walker <dwalker@...sta.com> wrote:
> On Wed, 2007-01-31 at 11:46 +0100, Ingo Molnar wrote:
> > * Daniel Walker <dwalker@...sta.com> wrote:
> >
> > > Uses the block notifier to replace the functionality of
> > > update_callback(). update_callback() was a special case specifically
> > > for the tsc, but including it in the clocksource structure duplicated
> > > it needlessly for other clocks.
> >
> > Firstly, it think it should be mentioned that Thomas' queue already
> > does this, in clocksource-remove-the-update-callback.patch (hence he
> > should have been Cc:-ed). Your queue 'drops' Thomas' patch then
> > redoes it here without mentioning that this is another version of
> > what is in Thomas's queue. So we get this situation:
> >
> > clocksource-remove-the-update-callback.patch
> > drop-clocksource-remove-the-update-callback.patch
> > clocksource_remove_update_callback.patch
> >
> > that all flip-flops the same thing.
>
> To be clear this change has exists for a very long time, long before
> Thomas implemented it ..
it doesnt matter who invented the wheel first, what matters is a clean
channel of communication so that we end up with the best code - and
leaving out Cc:s doesnt really help that.
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