From: Shuah Khan <shuahkh@osg.samsung.com>
To: Dave Hansen <dave.hansen@linux.intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/2] selftests, x86: updates for x86 protection keys self tests
Date: Wed, 8 Feb 2017 11:18:11 -0700 [thread overview]
Message-ID: <e91616e2-e9c3-71e7-e199-6be6c2b002c0@osg.samsung.com> (raw)
In-Reply-To: <20170203185132.E0B32D42@viggo.jf.intel.com>
On 02/03/2017 11:51 AM, Dave Hansen wrote:
> The memory protection keys selftests are spewing an uninitialized
> variable warning
>
> I also included a fix that affected the 32-bit version of the
> pkeys test case. It was parsing the siginfo incorrectly.
>
Dave,
Thanks. Applied to linux-kselftest next for 4.11-rc1
-- Shuah
prev parent reply other threads:[~2017-02-08 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 18:51 Dave Hansen
2017-02-03 18:51 ` [PATCH 1/2] selftests, x86, protection_keys: fix uninitialized variable warning Dave Hansen
2017-02-03 18:51 ` [PATCH 2/2] selftests, x86, protection_keys: fix wrong offset in siginfo Dave Hansen
2017-02-08 18:18 ` Shuah Khan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e91616e2-e9c3-71e7-e199-6be6c2b002c0@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®