From: Dave Hansen <dave.hansen@linux.intel.com>
To: Shuah Khan <shuahkh@osg.samsung.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org
Subject: Re: [PATCH 1/4] selftests, x86, protection_keys: fix unused variable compile warnings
Date: Thu, 2 Feb 2017 15:45:47 -0800 [thread overview]
Message-ID: <9c1b1172-ade9-b8c3-c7dc-5dc818504622@linux.intel.com> (raw)
In-Reply-To: <0262a979-6051-7007-f119-f45ede9449b7@osg.samsung.com>
On 02/02/2017 03:36 PM, Shuah Khan wrote:
> This patches is already in linux-kselftest next for 4.11
>
> Is there a reason why you chose to resend these.
Oh, my apologies! I didn't realize it had been picked up elsewhere.
Ingo had mentioned a few times in the last few days that he'd noticed
the warnings.
So, x86 maintainers, do we want these to go through the kselftest tree
or the x86 tree?
next prev parent reply other threads:[~2017-02-02 23:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 23:28 [PATCH 0/4] selftests, x86: updates for x86 protection keys self tests Dave Hansen
2017-02-02 23:28 ` [PATCH 1/4] selftests, x86, protection_keys: fix unused variable compile warnings Dave Hansen
2017-02-02 23:36 ` Shuah Khan
2017-02-02 23:45 ` Dave Hansen [this message]
2017-02-02 23:49 ` Shuah Khan
2017-02-03 6:43 ` Ingo Molnar
2017-02-02 23:28 ` [PATCH 2/4] selftests, x86, protection_keys: remove dead code Dave Hansen
2017-02-02 23:36 ` Shuah Khan
2017-02-02 23:28 ` [PATCH 3/4] selftests, x86, protection_keys: fix uninitialized variable warning Dave Hansen
2017-02-02 23:28 ` [PATCH 4/4] selftests, x86, protection_keys: fix wrong offset in siginfo Dave Hansen
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=9c1b1172-ade9-b8c3-c7dc-5dc818504622@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--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®