[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070110121409.GA28862@2ka.mipt.ru>
Date: Wed, 10 Jan 2007 15:14:09 +0300
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Jeff Garzik <jeff@...zik.org>
Cc: David Miller <davem@...emloft.net>,
Ulrich Drepper <drepper@...hat.com>,
Andrew Morton <akpm@...l.org>, netdev <netdev@...r.kernel.org>,
Zach Brown <zach.brown@...cle.com>,
Christoph Hellwig <hch@...radead.org>,
Chase Venters <chase.venters@...entec.com>,
Johann Borck <johann.borck@...sedata.com>,
linux-kernel@...r.kernel.org, Jamal Hadi Salim <hadi@...erus.ca>,
Ingo Molnar <mingo@...e.hu>, linux-fsdevel@...r.kernel.org
Subject: Re: [take32 0/10] kevent: Generic event handling mechanism.
On Wed, Jan 10, 2007 at 06:56:40AM -0500, Jeff Garzik (jeff@...zik.org) wrote:
> >It was there, but Andrew dropped it somewhere about take25 :)
>
> Probably because it was a moving target with a high rate of change,
> requiring time that Andrew did not have just to keep in sync and fix
> build conflicts with other -mm patches.
Ok, I understood.
Let's freeze kevent for a while and allow things to settle down, but...
How can I detect that it is in use, since I get no feedback?
I suppose that if Andrew will not pick it up, I will resend/push/pull
the latest set, but without new features implemented (or as addon), only
bugfixes.
> Jeff
>
--
Evgeniy Polyakov
-
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