Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754105Ab1EQKAm (ORCPT ); Tue, 17 May 2011 06:00:42 -0400 Received: from h5.dl5rb.org.uk ([81.2.74.5]:48059 "EHLO duck.linux-mips.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754024Ab1EQKAl (ORCPT ); Tue, 17 May 2011 06:00:41 -0400 Date: Tue, 17 May 2011 11:01:49 +0100 From: Ralf Baechle To: Kevin Cernekee Cc: Andrew Morton , Al Viro , Stephen Rothwell , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ipc: Add missing sys_ni entries for ipc/compat.c functions Message-ID: <20110517100149.GA7516@linux-mips.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1309 Lines: 39 On Fri, May 13, 2011 at 05:07:28PM -0700, Kevin Cernekee wrote: > Date: Fri, 13 May 2011 17:07:28 -0700 > From: Kevin Cernekee > To: Andrew Morton , Al Viro > , Stephen Rothwell > Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org > Subject: [PATCH] ipc: Add missing sys_ni entries for ipc/compat.c functions > Content-Type: text/plain; charset=us-ascii > > When building with: > > CONFIG_64BIT=y > CONFIG_MIPS32_COMPAT=y > CONFIG_COMPAT=y > CONFIG_MIPS32_O32=y > CONFIG_MIPS32_N32=y > CONFIG_SYSVIPC is not set > (and implicitly: CONFIG_SYSVIPC_COMPAT is not set) > > the final link fails with unresolved symbols for: > > compat_sys_semctl, compat_sys_msgsnd, compat_sys_msgrcv, > compat_sys_shmctl, compat_sys_msgctl, compat_sys_semtimedop > > The fix is to add cond_syscall declarations for all syscalls in > ipc/compat.c > > Signed-off-by: Kevin Cernekee Acked-by: Ralf Baechle Thanks, Kevin! Ralf -- 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/