From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: fadvise64
Date: Tue, 26 Aug 2003 01:02:57 +0200 [thread overview]
Message-ID: <20030825230257.GA8936@linux-mips.org> (raw)
Seems like there was no real possibility of anybody using the new 2.5
syscall fadvise64 with it's screwed prototype so I'm simply going to
avoid adding any extra junk to the kernel and change fadvise64 to
make the real thing that is call sys_fadvise64_64.
If that is going to cause any potencial trouble for example with libc,
let me know ...
Ralf
reply other threads:[~2003-08-25 23:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030825230257.GA8936@linux-mips.org \
--to=ralf@linux-mips.org \
--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