From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1423300AbcFGVYf (ORCPT <rfc822;w@1wt.eu>);
	Tue, 7 Jun 2016 17:24:35 -0400
Received: from mout.kundenserver.de ([212.227.126.134]:53208 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1160995AbcFGVYd (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 7 Jun 2016 17:24:33 -0400
From: Arnd Bergmann <arnd@arndb.de>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, linux-api@vger.kernel.org,
        linux-arch@vger.kernel.org, linux-mm@kvack.org,
        torvalds@linux-foundation.org, akpm@linux-foundation.org,
        dave.hansen@linux.intel.com
Subject: Re: [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls
Date: Tue, 07 Jun 2016 23:25:20 +0200
Message-ID: <4151348.Xje1rehFl0@wuerfel>
User-Agent: KMail/5.1.3 (Linux/4.4.0-22-generic; KDE/5.18.0; x86_64; ; )
In-Reply-To: <20160607204725.A731CB1E@viggo.jf.intel.com>
References: <20160607204712.594DE00A@viggo.jf.intel.com> <20160607204725.A731CB1E@viggo.jf.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:Cch9NAtoEnub7gha1lpGpGhmuHfSV4vgUZnrJa+J5jGatecZB3+
 zSf+4Yg/0/POxgD5Utnlrdg15z93dwmP9/eHR0iMcuvO9sNDDDu/QUGC31Zl+gXCylBn3mi
 A/rI3HSyx5yWES1JneK4nm733mEjBLvKlT1laeeiQsQFVam/bVIiOPMvER7wQFvNAKglM4T
 b7xlsF6nv8rffeUVAvPqA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:+r266JU1LYM=:/gaZL60gaGsl8OBtMYaoCc
 38M/m0jFK5o3dTLG08GqzAqjYMmbt5GTgrttxWNkaXCmldAmcfOe/Mz6YHEltXdYABH8ve3cd
 CnzqSSe3LgLK14SH36L7tY8Y/pG53RbO1EkRD5m+6CjvUY7tPxZr98G3JQMb3gEZ7n6vkIOZ3
 IjsG7Z8nh4FjG4dwDZkX4eOV6nrwEHaawdhQoGfv4h03fOw11CDu6A2q1A3zcwHC3wAzQbMMD
 UApJElTfaxqOdBnSFkpRlLv/VWcb14N++g0qtcR+xdODpdiB7f8duDrNNOT34Y5+VI3rfIkdZ
 Ym3izIgSm0kXeNz3E6LH2Jv+x6uOBvVjmlPXEUl8qkJebokTp19V0wwVvp3pTzgF2fucx8zw/
 UrezqTZng92oi1EeRmi1SfENw+xVm2who1IwMQrLEImoa+XiAaSC8Z61pzuz1Se99cFCoMl0M
 zF8h8Aa6G2AvcpC00uu5VZxBA5CyJITPIDkyLkQFJEnWhrHotgNBC8+JeWBSVb1THmaFPH24V
 tlP99B7wr5Ta1GVSYJsqFM514ZLBGS1uLmcKGsW33a/jpnWjEvB7W3FAKqTnqkN0xLS642tjA
 FpzUDMjooewJnNSo/gN/zupuOjtoho0+Qq179mEurIj/TPoMtRWf2PwKHCgfsEEuXd9EI2YQU
 xNry9T8385N8cC14j6++Meaa/oT/vIb8j8JgtbqQHiUGkElhLQyy75b6chDR3ZIFx0v4Bpm84
 NFu1XotKhzqfTt4a
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tuesday, June 7, 2016 1:47:25 PM CEST Dave Hansen wrote:
> From: Dave Hansen <dave.hansen@linux.intel.com>
> 
> These new syscalls are implemented as generic code, so enable
> them for architectures like arm64 which use the generic syscall
> table.
> 
> According to Arnd:
> 
>         Even if the support is x86 specific for the forseeable
>         future, it may be good to reserve the number just in
>         case.  The other architecture specific syscall lists are
>         usually left to the individual arch maintainers, most a
>         lot of the newer architectures share this table.
> 
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Cc: Arnd Bergmann <arnd@arndb.de>

Acked-by: Arnd Bergmann <arnd@arndb.de>

Thanks!