From: Andrew Morton <akpm@linux-foundation.org>
To: "Michael Kerrisk" <mtk.manpages@googlemail.com>
Cc: "Davide Libenzi" <davidel@xmailserver.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Where is the new timerfd?
Date: Fri, 23 Nov 2007 09:12:54 -0800 [thread overview]
Message-ID: <20071123091254.45f4193d.akpm@linux-foundation.org> (raw)
In-Reply-To: <cfd18e0f0711230439m1d72abdle4d5050b0bd935a1@mail.gmail.com>
On Fri, 23 Nov 2007 13:39:55 +0100 "Michael Kerrisk" <mtk.manpages@googlemail.com> wrote:
> On 11/23/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> > On Thu, 22 Nov 2007 16:35:38 -0800 (PST) Davide Libenzi
> > <davidel@xmailserver.org> wrote:
> >
> > > On Thu, 22 Nov 2007, Andrew Morton wrote:
> [...]
> > > > 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
> >
> > Half of us weren't born then ;)
> >
> > > Do you want me to repost?
> >
> > yes please.
>
> I suppose this means that timerfd will only go in for 2.6.25. I don't
> have a problem with that, but we better make sure that the existing
> timerfd in 2.6.24 is still disabled. (Andrew had a one liner for
> that, but I haven't checked if it's in place.)
>
I have no timerfd patches here.
next prev parent reply other threads:[~2007-11-23 17:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 11:24 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
2007-11-23 1:34 ` Andrew Morton
2007-11-23 12:39 ` Michael Kerrisk
2007-11-23 17:12 ` Andrew Morton [this message]
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=20071123091254.45f4193d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidel@xmailserver.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
all inboxes | Powered by JetHome®