Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Nov 2002 16:23:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Nov 2002 16:23:42 -0500 Received: from x35.xmailserver.org ([208.129.208.51]:5767 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id ; Mon, 18 Nov 2002 16:23:40 -0500 X-AuthUser: davidel@xmailserver.org Date: Mon, 18 Nov 2002 13:31:04 -0800 (PST) From: Davide Libenzi X-X-Sender: davide@blue1.dev.mcafeelabs.com To: Ulrich Drepper cc: Mark Mielke , Linux Kernel Mailing List Subject: Re: [rfc] epoll interface change and glibc bits ... In-Reply-To: <3DD946A2.7030501@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1252 Lines: 38 On Mon, 18 Nov 2002, Ulrich Drepper wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Davide Libenzi wrote: > > > epoll does hook f_op->poll() and hence uses the asm/poll.h bits. > > It does today. We are talking about "you promise that this will be the > case ever after or we'll cut your head off". I have no idea why you're > so reluctant since you don't have to maintain any of the user-level > bits. And it is not you who has to deal with the fallout of a change > when it happens. > > If epoll is so different from poll (and this is what I've been told frmo > Davide) then there should be a clear separation of the interfaces and > all those arguing to unify the data types and constants better should > rethink there understanding. Ok, the message has been post and noone argued about your solution. Like it is used to say "speak now or forever hold your piece" :) So we will go with it, no problem for me. We will define a struct epollfd and all POLL* bits in EPOLL* - Davide - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/