From: Daniel Jacobowitz <dan@debian.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org, kraj@mvista.com,
libc-ports@sourceware.org
Subject: Re: [PATCH] Fix some system calls with long long arguments
Date: Wed, 23 May 2007 13:26:40 -0400 [thread overview]
Message-ID: <20070523172640.GC29019@caradoc.them.org> (raw)
In-Reply-To: <20070518.004759.59650774.anemo@mba.ocn.ne.jp>
On Fri, May 18, 2007 at 12:47:59AM +0900, Atsushi Nemoto wrote:
> On Fri, 18 May 2007 00:46:13 +0900 (JST), Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
> > I fixed N32/O32 readahead, sync_file_range, fadvise, fadvise64
> > syscalls on both kernel and glibc side.
> >
> > Here is a kernel side fixes.
>
> And here is glibc side fixes for posix_fadvise, posix_fadvise64,
> readahead, sync_file_range. For O32, add a padding before a long long
> argument pair. For N32, pass a long long value by one argument. O32
> readahead borrows ARM EABI implementation. N32 posix_fadvise64 use C
> implementation (instead of syscalls.list) for versioned symbols.
I see the kernel patch was already merged; I've added this to CVS.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-05-23 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:39 [PATCH] Fix some system calls with long long arguments Atsushi Nemoto
2007-03-07 14:14 ` Atsushi Nemoto
2007-03-08 15:37 ` Atsushi Nemoto
2007-03-15 1:35 ` Atsushi Nemoto
2007-03-15 16:33 ` Atsushi Nemoto
2007-03-15 16:53 ` Atsushi Nemoto
2007-05-17 15:46 ` Atsushi Nemoto
2007-05-17 15:47 ` Atsushi Nemoto
2007-05-21 4:38 ` Atsushi Nemoto
2007-05-23 17:26 ` Daniel Jacobowitz [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=20070523172640.GC29019@caradoc.them.org \
--to=dan@debian.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=kraj@mvista.com \
--cc=libc-ports@sourceware.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 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.