From: Richard Sandiford <richard@codesourcery.com>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH] The o32 fstatat syscall behaves differently on 32 and 64 bit kernels
Date: Sun, 17 Sep 2006 21:03:24 +0100 [thread overview]
Message-ID: <873baqxnub.fsf@talisman.home> (raw)
In-Reply-To: <87bqpexpcp.fsf@talisman.home> (Richard Sandiford's message of "Sun, 17 Sep 2006 20:30:46 +0100")
Richard Sandiford <richard@codesourcery.com> writes:
> I think this is just a case of a compat too far. The o32 stat64 is the
> same as plain stat on n64, so 64-bit kernels can just use newfstatat.
> (n32 already does this, and works correctly as-is.)
Huh. The last sentence sounded like a really useful addition when I
wrote it, but even so soon after the fact, I've no idea why. It sounds
like I was implying that stat calls require conversion on n32, but that
certainly wasn't my intention. Please ignore. ;)
Richard
prev parent reply other threads:[~2006-09-17 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 19:30 [PATCH] The o32 fstatat syscall behaves differently on 32 and 64 bit kernels Richard Sandiford
2006-09-17 20:03 ` Richard Sandiford [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=873baqxnub.fsf@talisman.home \
--to=richard@codesourcery.com \
--cc=linux-mips@linux-mips.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