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 S1752051AbdBBX2p (ORCPT <rfc822;w@1wt.eu>);
        Thu, 2 Feb 2017 18:28:45 -0500
Received: from mga14.intel.com ([192.55.52.115]:49219 "EHLO mga14.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751622AbdBBX2o (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 2 Feb 2017 18:28:44 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,326,1477983600"; 
   d="scan'208";a="60580406"
Subject: [PATCH 0/4] selftests, x86: updates for x86 protection keys self tests
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>
From: Dave Hansen <dave.hansen@linux.intel.com>
Date: Thu, 02 Feb 2017 15:28:42 -0800
Message-Id: <20170202232842.C3C30DB2@viggo.jf.intel.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

The memory protection keys selftests are spewing warnings.  This
fixes them up.  Thanks, Shuah, for sending these first two a few
weeks ago!  I wrongly assumed they would get picked up somewhere.

I also included a fix that affected the 32-bit version of the
pkeys test case.  It was parsing the siginfo incorrectly.