linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ben@decadent.org.uk
Cc: bfields@fieldses.org, torvalds@linux-foundation.org,
	neilb@suse.de, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] All Arch: remove linkage for sys_nfsservctl system call
Date: Fri, 26 Aug 2011 20:01:09 -0400 (EDT)	[thread overview]
Message-ID: <20110826.200109.1784685596300352827.davem@davemloft.net> (raw)
In-Reply-To: <20110826233258.GE24107@decadent.org.uk>

From: Ben Hutchings <ben@decadent.org.uk>
Date: Sat, 27 Aug 2011 00:32:58 +0100

> On Fri, Aug 26, 2011 at 06:03:11PM -0400, J. Bruce Fields wrote:
> [...]
>> diff --git a/arch/sparc/kernel/systbls_64.S b/arch/sparc/kernel/systbls_64.S
>> index f566518..c9296ab 100644
>> --- a/arch/sparc/kernel/systbls_64.S
>> +++ b/arch/sparc/kernel/systbls_64.S
>> @@ -145,7 +145,7 @@ sys_call_table:
>>  	.word sys_fstatfs64, sys_llseek, sys_mlock, sys_munlock, sys_mlockall
>>  /*240*/	.word sys_munlockall, sys_sched_setparam, sys_sched_getparam, sys_sched_setscheduler, sys_sched_getscheduler
>>  	.word sys_sched_yield, sys_sched_get_priority_max, sys_sched_get_priority_min, sys_sched_rr_get_interval, sys_nanosleep
>> -/*250*/	.word sys_64_mremap, sys_sysctl, sys_getsid, sys_fdatasync, sys_nfsservctl
>> +/*250*/	.word sys_64_mremap, sys_sysctl, sys_getsid, sys_fdatasync, sys_nis_syscall
> [...]
>           	                                                                  ^
> This seems to be a typo for 'sys_ni_syscall'.

It's intentional, look at the sparc sources.

  parent reply	other threads:[~2011-08-27  0:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1312810169.2591.1153.camel@deadeye>
     [not found] ` <20110808155538.GB904@fieldses.org>
     [not found]   ` <20110808180658.GC29924@decadent.org.uk>
     [not found]     ` <20110808180658.GC29924-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2011-08-26 22:03       ` [PATCH] All Arch: remove linkage for sys_nfsservctl system call J. Bruce Fields
2011-08-26 22:03         ` J. Bruce Fields
2011-08-26 23:32         ` Ben Hutchings
     [not found]           ` <20110826233258.GE24107-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org>
2011-08-26 23:52             ` J. Bruce Fields
2011-08-26 23:52               ` J. Bruce Fields
2011-08-27  0:01           ` David Miller [this message]
2011-08-27 14:39         ` Mike Frysinger
2011-08-28 21:12         ` David Miller
2011-08-28 23:50         ` Tony Breeds
2011-08-28 23:50           ` Tony Breeds
     [not found]         ` <20110826220311.GA18140-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-08-29 22:57           ` Stephen Rothwell
2011-08-29 22:57             ` Stephen Rothwell
2011-08-29 23:11             ` NeilBrown
     [not found]               ` <20110830091150.176cd08c-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2011-08-31 13:46                 ` J. Bruce Fields
2011-08-31 13:46                   ` J. Bruce Fields
2011-08-31 10:15     ` David Howells

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=20110826.200109.1784685596300352827.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ben@decadent.org.uk \
    --cc=bfields@fieldses.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).