From: Arnd Bergmann <arnd@arndb.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Subject: Re: [PATCH 2/7] rename the provided execve functions to kernel_execve
Date: Mon, 28 Aug 2006 09:44:21 +0200
User-Agent: KMail/1.9.1
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
       Jeff Dike <jdike@addtoit.com>, Bjoern Steinbrink <B.Steinbrink@gmx.de>,
       Arjan van de Ven <arjan@infradead.org>,
       Chase Venters <chase.venters@clientec.com>,
       Andrew Morton <akpm@osdl.org>, Russell King <rmk+lkml@arm.linux.org.uk>,
       rusty@rustcorp.com.au
References: <20060827214734.252316000@klappe.arndb.de> <20060827215636.091665000@klappe.arndb.de> <20060827192030.633cf467.rdunlap@xenotime.net>
In-Reply-To: <20060827192030.633cf467.rdunlap@xenotime.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200608280944.21819.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 819
Lines: 19

On Monday 28 August 2006 04:20, Randy.Dunlap wrote:
> Question:
> All other syscalls (in syscalls.h) return long or unsigned long
> or ssize_t etc. ?I.e., none of them return int. ?Does this one
> return int because it's strictly an inside-the-kernel "syscall",
> not exposed to userspace?

Well, it's not really a system call in the first place, but
I could not find any other place where it would fit.
The prototype of the kernel_execve function is the one from
the man execve page, and also similar to those that were
generated by the _syscall3() macro before.

	Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/