All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Riku Voipio <riku.voipio@iki.fi>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add futimesat syscall
Date: Thu, 18 Sep 2008 13:13:40 +0200	[thread overview]
Message-ID: <20080918111340.GB19245@networkno.de> (raw)
In-Reply-To: <20080918101629.GB9799@localhost.localdomain>

Kirill A. Shutemov wrote:
> On Thu, Sep 18, 2008 at 12:42:34PM +0300, Riku Voipio wrote:
> > On Thu, Sep 18, 2008 at 12:28:31PM +0300, Kirill A. Shutemov wrote:
> > > On Thu, Sep 18, 2008 at 12:08:21PM +0300, Riku Voipio wrote:
> > > I don't think that it's great idea. If libc/kernel headers doesn't provide
> > > the syscall we shouldn't implement them. The exception is syscalls without
> > > libc's wrapper. Like gettid(2).
> > 
> > Well, defining syscalls appears to be a common practice in qemu for the
> > *at family of syscalls (openat, linkat, ...), so it doesn't seem that
> > far off for futimesat().
> 
> *at syscalls ware implemented in linux 2.6.16. glibc's wrappers to this
> syscalls were implemented in glibc 2.4. Both of them relesed more than two
> and half years ago.
> 
> I think we can drop this crap now.

Current Debian stable uses glibc 2.3.6.


Thiemo

  reply	other threads:[~2008-09-18 11:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 19:45 [Qemu-devel] [PATCH] add futimesat syscall Riku Voipio
2008-09-17 23:54 ` andrzej zaborowski
2008-09-18  5:00   ` Kirill A. Shutemov
2008-09-18  6:30   ` Riku Voipio
2008-09-18  7:23     ` Laurent Desnogues
2008-09-18  9:08       ` Riku Voipio
2008-09-18  9:28         ` Kirill A. Shutemov
2008-09-18  9:42           ` Riku Voipio
2008-09-18 10:16             ` Kirill A. Shutemov
2008-09-18 11:13               ` Thiemo Seufer [this message]
2008-09-18 11:45                 ` Kirill A. Shutemov

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=20080918111340.GB19245@networkno.de \
    --to=ths@networkno.de \
    --cc=kirill@shutemov.name \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.