From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schwab Subject: Re: Drop IPC_OLD for direct ipc syscalls? Date: Sun, 20 Sep 2015 12:38:46 +0200 Message-ID: <87pp1dv0i1.fsf@igel.home> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mail-out.m-online.net ([212.18.0.10]:48066 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754833AbbITKiy (ORCPT ); Sun, 20 Sep 2015 06:38:54 -0400 In-Reply-To: (Geert Uytterhoeven's message of "Sun, 20 Sep 2015 11:07:28 +0200") Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Geert Uytterhoeven Cc: Greg Ungerer , Linux/m68k , "linux-kernel@vger.kernel.org" , Linux-Arch , Arnd Bergmann , Andy Lutomirski , Ingo Molnar , "H. Peter Anvin" Geert Uytterhoeven writes: > Should I postpone wiring up the direct ipc syscalls on m68k (and thus renumber > __NR_membarrier) until the above is resolved, or can they go in in v4.3? If you wire up the direct ipc calls know you create an ABI that is harder to get rid of. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."