Re: [take32 0/10] kevent: Generic event handling mechanism.

On Wed, Jan 10, 2007 at 06:56:40AM -0500, Jeff Garzik ([email protected]) 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [take32 0/10] kevent: Generic event handling mechanism.
    • From: Evgeniy Polyakov <[email protected]>
  • Re: [take32 0/10] kevent: Generic event handling mechanism.
    • From: Jeff Garzik <[email protected]>
  • Re: [take32 0/10] kevent: Generic event handling mechanism.
    • From: Evgeniy Polyakov <[email protected]>
  • Re: [take32 0/10] kevent: Generic event handling mechanism.
    • From: Jeff Garzik <[email protected]>

• Prev by Date: Re: [PATCH 2.6.20-rc4 1/4] futex priority based wakeup
• Next by Date: Re: macros: "do-while" versus "({ })" and a compile-time error
• Previous by thread: Re: [take32 0/10] kevent: Generic event handling mechanism.
• Next by thread: Kevent bonus: epoll implementaion over kevent.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]