From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:40336 "EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP id S1161022AbWASB0m (ORCPT ); Wed, 18 Jan 2006 20:26:42 -0500 Date: Wed, 18 Jan 2006 17:26:39 -0800 (PST) Message-Id: <20060118.172639.15928930.davem@davemloft.net> Subject: Re: new syscalls From: "David S. Miller" In-Reply-To: References: <20060118133629.1cda96fd.akpm@osdl.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org To: davidel@xmailserver.org Cc: akpm@osdl.org, tony.luck@intel.com, linux-arch@vger.kernel.org, janak@us.ibm.com, drepper@redhat.com, dwmw2@infradead.org, dhowells@redhat.com, christoph@lameter.com List-ID: From: Davide Libenzi Date: Wed, 18 Jan 2006 17:17:20 -0800 (PST) > How sophisticated this has to be? And what's the expected ETA? The > epoll_pwait is really a wrapper around epoll_wait (that did not change at > all), so the test in this case should just make sure that the signal > behaviour is the one expected. Something along the lines of a smoke test is probably sufficient. The platform folks just want to make sure they wired up the syscall tables correctly, for the most part.