From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, drepper@redhat.com,
mtk-manpages@gmx.net, nickpiggin@yahoo.com.au
Subject: Re: [patch 1/1] sys_sync_file_range()
Date: Tue, 4 Apr 2006 14:01:40 -0700 [thread overview]
Message-ID: <20060404140140.f13b8606.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060404205055.GA5745@agluck-lia64.sc.intel.com>
On Tue, 4 Apr 2006 13:50:55 -0700 Luck, Tony wrote:
> On Wed, Mar 29, 2006 at 11:41:11PM -0800, akpm@osdl.org wrote:
> > @@ -318,8 +318,9 @@
> > #define __NR_unshare 310
> > #define __NR_set_robust_list 311
> > #define __NR_get_robust_list 312
> > +#define __NR_sys_sync_file_range 313
>
> What's up with the __NR_sys_yada_yada? Except for recent entries (kexec,
> splice, and now sync_file_range) all of the other names in here have
> dropped the "sys_".
>
> Is it too late to fix __NR_sys_kexec_load (since it is out in the
> wild now?)
already been done: (copy-n-paste warning here:)
~~~~~
On i386, we don't use sys_ prefix for __NR_*. This patch removes it.
[FWIW, _syscall*() macros will generate foo() instead of sys_foo().]
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
include/asm-i386/unistd.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN include/asm-i386/unistd.h~remove-sys_-prefix include/asm-i386/unistd.h
--- linux-2.6/include/asm-i386/unistd.h~remove-sys_-prefix 2006-04-02 05:23:57.000000000 +0900
+++ linux-2.6-hirofumi/include/asm-i386/unistd.h 2006-04-02 05:24:10.000000000 +0900
@@ -318,8 +318,8 @@
#define __NR_unshare 310
#define __NR_set_robust_list 311
#define __NR_get_robust_list 312
-#define __NR_sys_splice 313
-#define __NR_sys_sync_file_range 314
+#define __NR_splice 313
+#define __NR_sync_file_range 314
#define NR_syscalls 315
---
~Randy
next prev parent reply other threads:[~2006-04-04 20:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 7:41 akpm
2006-03-30 7:58 ` Neil Brown
2006-03-30 8:11 ` Andrew Morton
2006-03-30 8:32 ` Andrew Morton
2006-03-30 8:55 ` Neil Brown
2006-03-30 15:31 ` OGAWA Hirofumi
2006-03-30 20:19 ` Andrew Morton
2006-03-30 21:17 ` Nathan Scott
2006-04-03 1:24 ` Neil Brown
2006-04-03 7:50 ` Jens Axboe
2006-04-03 8:27 ` Andrew Morton
2006-04-03 14:31 ` Jens Axboe
2006-04-03 21:21 ` Andrew Morton
2006-04-04 20:50 ` Luck, Tony
2006-04-04 21:00 ` Andrew Morton
2006-04-04 21:01 ` Randy.Dunlap [this message]
2006-04-04 21:03 ` Ulrich Drepper
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=20060404140140.f13b8606.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=nickpiggin@yahoo.com.au \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®