From: Andrew Morton <akpm@linux-foundation.org>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: davidel@xmailserver.org, vda.linux@googlemail.com,
rdunlap@xenotime.net, tglx@linutronix.de,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
drepper@redhat.com, stable@kernel.org, hch@lst.de,
jengelh@computergmbh.de, corbet@lwn.net
Subject: Re: timerfd redux
Date: Thu, 13 Sep 2007 01:20:44 -0700 [thread overview]
Message-ID: <20070913012044.c120d98f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070913081359.216550@gmx.net>
On Thu, 13 Sep 2007 10:13:59 +0200 "Michael Kerrisk" <mtk-manpages@gmx.net> wrote:
> Andrew,
>
> > > 3. possible solutions
> >
> > I don't think we'll have this settled and coded in time for 2.6.23. So I
> > think the prudent thing to do is to push this back to 2.6.24 and not offer
> > sys_timerfd() in 2.6.23.
>
> Did you want a patch to remove the syscall number for now,
> or will you do that?
>
Please send one over sometime.
prev parent reply other threads:[~2007-09-13 8:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 6:41 [PATCH] Revised timerfd() interface Michael Kerrisk
2007-08-30 12:01 ` Davide Libenzi
2007-09-04 8:03 ` Michael Kerrisk
2007-09-04 8:18 ` Andrew Morton
2007-09-04 8:24 ` Michael Kerrisk
2007-09-04 15:25 ` Davide Libenzi
2007-09-04 15:39 ` Michael Kerrisk
2007-09-04 22:41 ` Davide Libenzi
2007-09-04 20:49 ` Michael Kerrisk
2007-09-04 22:44 ` Davide Libenzi
2007-09-05 0:08 ` Michael Kerrisk
2007-09-05 12:02 ` Andrew Morton
2007-09-05 16:14 ` Davide Libenzi
2007-09-05 16:23 ` Michael Kerrisk
2007-09-05 19:57 ` Davide Libenzi
2007-09-05 22:50 ` Michael Kerrisk
2007-09-05 23:45 ` Davide Libenzi
2007-09-06 6:58 ` Michael Kerrisk
2007-09-06 23:37 ` Davide Libenzi
2007-09-10 3:15 ` Michael Kerrisk
2007-09-05 12:12 ` Denys Vlasenko
2007-09-05 15:32 ` timerfd redux Michael Kerrisk
2007-09-13 2:39 ` Andrew Morton
2007-09-13 6:14 ` Michael Kerrisk
2007-09-13 8:13 ` Michael Kerrisk
2007-09-13 8:20 ` Andrew Morton [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=20070913012044.c120d98f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davidel@xmailserver.org \
--cc=drepper@redhat.com \
--cc=hch@lst.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vda.linux@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
Powered by JetHome