mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] eventfd, signalfd, timerfd, epoll_create w/flags
Date: Sun, 27 Apr 2008 17:07:29 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0804271703470.18184@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <48150BDA.5070903@redhat.com>

On Sun, 27 Apr 2008, Ulrich Drepper wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Davide Libenzi wrote:
> 
> > Ok, I asked this myself for about ten minutes, than I gave up. But why 
> > sys_epoll_createp() instead of sys_epoll_create2()? There MUST be a reason 
> > to deviate from the standard of all the other ones...
> 
> I used the number at the end for syscalls which aren't visible at
> userlevel.  There they are useful indicating the number of arguments.
> At userlevel I personally find it less than optimal but I'd have no
> problem changing it to epoll_create2.

I think that an ending '2' at least has the logic behind of telling the 
number of parameters. A 'p' really doesn't say anything.
So it's either gonna be something like epoll_create_flags() or 
epoll_create2(). And between the two, I'd personally pick the latter.



- Davide



  parent reply	other threads:[~2008-04-28  0:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 22:17 Ulrich Drepper
2008-04-27 23:20 ` Davide Libenzi
2008-04-27 23:27   ` Ulrich Drepper
2008-04-27 23:31     ` H. Peter Anvin
2008-04-27 23:33       ` Ulrich Drepper
2008-04-27 23:38         ` H. Peter Anvin
2008-04-28  0:07     ` Davide Libenzi [this message]
2008-04-28  7:12   ` Michael Kerrisk

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.0804271703470.18184@alien.or.mcafeemobile.com \
    --to=davidel@xmailserver.org \
    --cc=akpm@linux-foundation.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®