public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Greg Hackmann <ghackmann@google.com>
Cc: Pavel Labath <labath@google.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests: breakpoint: add step_after_suspend_test
Date: Tue, 23 Feb 2016 11:27:38 -0700	[thread overview]
Message-ID: <56CCA49A.2000706@osg.samsung.com> (raw)
In-Reply-To: <1456164657-102353-1-git-send-email-ghackmann@google.com>

On 02/22/2016 11:10 AM, Greg Hackmann wrote:
> Commit e56d82a11617 ("arm64: cpu hotplug: ensure we mask out
> CPU_TASKS_FROZEN in notifiers") fixed a long-standing ARM64 bug that
> broke single-stepping after a suspend/resume cycle.  Add a kernel
> selftest to make sure this doesn't regress or affect other platforms.
> 
> Signed-off-by: Greg Hackmann <ghackmann@google.com>
> ---
>  tools/testing/selftests/breakpoints/Makefile       |   4 +-
>  .../breakpoints/step_after_suspend_test.c          | 219 +++++++++++++++++++++
>  2 files changed, 222 insertions(+), 1 deletion(-)
>  create mode 100644 tools/testing/selftests/breakpoints/step_after_suspend_test.c
> 

Thanks for the patch. There is a whitespace
error which I fixed. No need to resend this
patch. Please make sure to run checkpatch.pl
on your future patches.

Applied to linux-kselftest next for 4.6-rc1

thanks,
-- Shuah


-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978

      reply	other threads:[~2016-02-23 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 18:10 [PATCH] selftests: breakpoint: add step_after_suspend_test Greg Hackmann
2016-02-23 18:27 ` 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=56CCA49A.2000706@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=ghackmann@google.com \
    --cc=labath@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.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