public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Shuah Khan <shuah@kernel.org>, Darren Hart <dvhart@linux.intel.com>
Cc: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stafford Horne <shorne@gmail.com>
Subject: [PATCH v2 0/6] Selftests fixes for futex and intel_pstate
Date: Thu, 12 Jan 2017 00:11:13 +0900	[thread overview]
Message-ID: <cover.1484147115.git.shorne@gmail.com> (raw)

This is followup to my previous patch [1] which was a very simple makefile
change. After a comment from Darren Hart I updated intel_pstate as well,
but noticed a few issues with running intel_pstate. That caused the change
to expand a bit.

 - fix build deps for futex test *original*
 - update makefile for intel_pstate to be in sync with Bamvor's changes
 - update cpupower frequency-info to fix intel_pstate test

For the linux-pm list the change to cpupower might be an issue, but if so
it would be nice if they can suggest a better way to get the self test to
do what it wants to do.

The series is based on Shuah's kselftest next branch, because that is
where Bamvor's latest changes are:
 git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next

[1] https://lkml.org/lkml/2017/1/5/903

Stafford Horne (6):
  selftests/futex: Add stdio used for logging
  selftests/futex: Add headers to makefile dependencies
  cpupower: Restore format of frequency-info limit
  selftests/intel_pstate: Fix warning on loop index overflow
  selftests/intel_pstate: Update makefile to match new style
  selftests: Add intel_pstate to TARGETS

 tools/power/cpupower/utils/cpufreq-info.c         | 21 ++++++++++++---------
 tools/testing/selftests/Makefile                  |  1 +
 tools/testing/selftests/futex/functional/Makefile |  5 ++++-
 tools/testing/selftests/futex/include/logging.h   |  1 +
 tools/testing/selftests/intel_pstate/Makefile     | 13 ++++---------
 tools/testing/selftests/intel_pstate/aperf.c      |  2 +-
 6 files changed, 23 insertions(+), 20 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-01-11 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 15:11 Stafford Horne [this message]
2017-01-11 15:11 ` [PATCH v2 1/6] selftests/futex: Add stdio used for logging Stafford Horne
     [not found] ` <cover.1484146515.git.shorne@gmail.com>
2017-01-11 15:11   ` [PATCH v2 2/6] cpupower: Restore format of frequency-info limit Stafford Horne
2017-01-11 15:20     ` Stafford Horne
2017-01-11 15:11 ` [PATCH v2 2/6] selftests/futex: Add headers to makefile dependencies Stafford Horne
2017-01-11 15:16 ` [PATCH v2 3/6] cpupower: Restore format of frequency-info limit Stafford Horne
2017-01-11 15:16 ` [PATCH v2 4/6] selftests/intel_pstate: Fix warning on loop index overflow Stafford Horne
2017-01-11 15:16 ` [PATCH v2 5/6] selftests/intel_pstate: Update makefile to match new style Stafford Horne
2017-01-11 15:16 ` [PATCH v2 6/6] selftests: Add intel_pstate to TARGETS Stafford Horne
2017-01-19 17:35 ` [PATCH v2 0/6] Selftests fixes for futex and intel_pstate Shuah Khan
2017-01-19 22:42   ` Stafford Horne

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=cover.1484147115.git.shorne@gmail.com \
    --to=shorne@gmail.com \
    --cc=bamvor.zhangjian@linaro.org \
    --cc=dvhart@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@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