Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org, richard@codesourcery.com
Subject: Re: [PATCH] fstatat syscall names
Date: Tue, 19 Sep 2006 23:44:41 +0100	[thread overview]
Message-ID: <20060919224441.GA4031@linux-mips.org> (raw)
In-Reply-To: <877j02xozk.fsf@talisman.home>

On Sun, Sep 17, 2006 at 08:38:39PM +0100, Richard Sandiford wrote:

> MIPS is the only port to call its fstatat()-related syscalls
> "__NR_fstatat".  Now I can see why that might be seen as every
> other port being wrong, but I think for o32, it is at best confusing.
> __NR_fstat provides a plain (32-bit) stat while __NR_fstatat provides a
> 64-bit stat.  Changing the name to __NR_fstatat64 would make things more
> explicit, match x86, and make the glibc port slightly easier.
> 
> The current name is more appropriate for n32 and n64, but it would be
> appropriate for other 64-bit targets too, and those targets have chosen
> to call it __NR_newfstatat instead.  Using the same name for MIPS would
> again be more consistent and make the glibc port slightly easier.
> 
> I'm not wedded to this idea if the current names are preferred,
> but FWIW...

I may have prefered the current naming at the time because they seemed to
be more logical to me when I choose those names but I'm not married to
them either.

  Ralf

      reply	other threads:[~2006-09-19 22:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17 19:38 [PATCH] fstatat syscall names Richard Sandiford
2006-09-19 22:44 ` Ralf Baechle [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=20060919224441.GA4031@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=richard@codesourcery.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