From: Davide Libenzi <davidel@xmailserver.org>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC,PATCH] poll cleanup 2/3
Date: Sun, 10 Nov 2002 14:08:13 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.44.0211101407360.7415-100000@blue1.dev.mcafeelabs.com> (raw)
In-Reply-To: <3DCE435D.10604@colorfullife.com>
On Sun, 10 Nov 2002, Manfred Spraul wrote:
> Change 2:
> split the poll_table structure into 2 parts:
> One global part with just a function pointer and a priv variable.
> The 2nd part is user specific:
> for __pollwait: the poll table and the error variable
> for ep_ptable_queue_proc: the pointer to the eventpoll data.
>
> This change is a prerequisite for the next patch, that embedds a few
> waitqueues in the __pollwait specific part of the poll structure.
Manfred, I can ack this with the changes I told you inside fs/eventpoll.c
- Davide
prev parent reply other threads:[~2002-11-10 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 11:30 [RFC,PATCH] poll cleanup 2/3 Manfred Spraul
2002-11-10 22:08 ` Davide Libenzi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0211101407360.7415-100000@blue1.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).