From: Darren Hart <dvhart@linux.intel.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: <linux-api@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Davidlohr Bueso <dave@stgolabs.net>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<fengguang.wu@intel.com>, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [GIT PULL] selftest: Add futex functional tests
Date: Tue, 31 Mar 2015 09:24:18 -0700 [thread overview]
Message-ID: <D14017F7.C46F0%dvhart@linux.intel.com> (raw)
In-Reply-To: <551ABE00.9050003@osg.samsung.com>
On 3/31/15, 8:32 AM, "Shuah Khan" <shuahkh@osg.samsung.com> wrote:
>Hi Daren,
>
>On 03/27/2015 04:17 PM, Darren Hart wrote:
>> Hi Shuah,
>>
>> This series begins the process of migrating my futextest tests into
>>kselftest.
>> I've started with only the functional tests, as the performance and
>>stress may
>> not be appropriate for kselftest as they stand.
>>
>> I cleaned up various complaints from checkpatch, but I ignored others
>>that would
>> require significant rework of the testcases, such as not using volatile
>>and not
>> creating new typedefs.
>>
>> The patches will follow, but I'm providing a pull request for your
>>convenience
>> as well.
>
>Thanks for acting on this so quickly after we talked about it at ELC.
>Just a quick note that I am going to get to this soon once I get the
>4.1 content wrapped up. We can plan upon getting these into 4.2.
OK. Michael E. provided some feedback which I can either incorporate and
respin, or I can send as a follow-on to your -next after you merge these.
Which do you prefer?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-31 16:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 22:17 [GIT PULL] selftest: Add futex functional tests Darren Hart
2015-03-27 22:17 ` [PATCH 1/5] selftests: " Darren Hart
2015-05-06 17:28 ` Shuah Khan
2015-05-06 18:04 ` Darren Hart
2015-03-27 22:17 ` [PATCH 2/5] selftest/futex: Update Makefile to use lib.mk Darren Hart
2015-03-29 23:49 ` Michael Ellerman
2015-03-30 16:31 ` Darren Hart
2015-03-31 23:28 ` Michael Ellerman
2015-03-27 22:17 ` [PATCH 3/5] selftest/futex: Increment ksft pass and fail counters Darren Hart
2015-03-27 22:17 ` [PATCH 4/5] selftest: Add futex tests to the top-level Makefile Darren Hart
2015-03-27 22:17 ` [PATCH 5/5] kselftest: Add exit code defines Darren Hart
2015-03-27 22:59 ` Michael Ellerman
2015-03-27 23:09 ` Darren Hart
2015-03-29 23:44 ` Michael Ellerman
2015-03-30 16:26 ` Darren Hart
2015-03-30 16:30 ` Peter Zijlstra
[not found] ` <551ABE00.9050003@osg.samsung.com>
2015-03-31 16:24 ` Darren Hart [this message]
2015-03-31 16:37 ` [GIT PULL] selftest: Add futex functional tests Shuah Khan
2015-04-08 4:12 ` Darren Hart
2015-04-09 5:41 ` Shuah Khan
2015-04-09 5:44 ` Darren Hart
2015-05-06 18:34 ` Davidlohr Bueso
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=D14017F7.C46F0%dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=dave@stgolabs.net \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=shuahkh@osg.samsung.com \
--cc=tglx@linutronix.de \
/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