From: Davide Libenzi <davidel@xmailserver.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Where is the new timerfd?
Date: Thu, 22 Nov 2007 16:35:38 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711221634510.7431@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <20071122162430.48f55995.akpm@linux-foundation.org>
On Thu, 22 Nov 2007, Andrew Morton wrote:
> On Thu, 22 Nov 2007 11:46:13 -0800 (PST) Davide Libenzi <davidel@xmailserver.org> wrote:
>
> > On Thu, 22 Nov 2007, Michael Kerrisk wrote:
> >
> > > On Nov 22, 2007 6:34 PM, Davide Libenzi <davidel@xmailserver.org> wrote:
> > > > On Thu, 22 Nov 2007, Michael Kerrisk wrote:
> > > >
> > > > > Hey Davide,
> > > > >
> > > > > Where is the new timerfd API. In 2.6.24-rc3, I see the *old* API...
> > > >
> > > > Maybe Andrew stuffed the turkey with it? :) It was there. I remeber it was
> > > > merged. Some screw up reverted it?
> > >
> > > t looks that way.
> >
> > I'm looking at the log now. It never went in actually. Andrew-san, what
> > happened?
> >
>
> Last I recall, we removed the API for 2.6.23 because we intended to do a
> different interface for 2.6.24.
>
> But I don't recall seeing any timerfd patches in maybe a month.
Was sent on Sep 23, Subject: new timerfd API
Do you want me to repost?
- Davide
next prev parent reply other threads:[~2007-11-23 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 11:24 Where is the new timerfd? Michael Kerrisk
2007-11-22 17:34 ` Davide Libenzi
2007-11-22 18:48 ` Michael Kerrisk
2007-11-22 19:46 ` Davide Libenzi
2007-11-23 0:24 ` Andrew Morton
2007-11-23 0:35 ` Davide Libenzi [this message]
2007-11-23 1:34 ` Andrew Morton
2007-11-23 12:39 ` Michael Kerrisk
2007-11-23 17:12 ` Andrew Morton
2007-11-23 17:29 ` Davide Libenzi
2007-11-23 18:38 ` Ulrich Drepper
2007-11-23 19:14 ` Michael Kerrisk
2007-11-23 21:01 ` Davide Libenzi
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.64.0711221634510.7431@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@googlemail.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).