public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	Namhyung Kim <namhyung@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove redhat'ism from ftrace selftests.
Date: Thu, 5 Mar 2015 10:17:04 -0500	[thread overview]
Message-ID: <20150305151704.GA24554@codemonkey.org.uk> (raw)
In-Reply-To: <54F872E2.9000708@osg.samsung.com>

On Thu, Mar 05, 2015 at 08:14:42AM -0700, Shuah Khan wrote:
 > On 03/04/2015 06:18 PM, Michael Ellerman wrote:
 > > On Wed, 2015-03-04 at 21:44 +0900, Namhyung Kim wrote:
 > >>
 > >> I think that there's no need to even call true or echo..
 > >>
 > >> From 0549544e8e982df6478f11e2b4fe419f94c22434 Mon Sep 17 00:00:00 2001
 > >> From: Namhyung Kim <namhyung@kernel.org>
 > >> Date: Wed, 4 Mar 2015 21:26:38 +0900
 > >> Subject: [PATCH] ftracetest: Do not use usleep
 > >>
 > >> The usleep is only provided on distros from Redhat so running ftracetest
 > >> on other distro resulted in failures due to the missing usleep.
 > >>
 > >> The reason of using [u]sleep in the test was to generate (scheduler)
 > >> events.  But as we use 'cat trace | grep | wc -l' to read the events,
 > >> the command themselves already generate some events before reading the
 > >> trace file so no need to call [u]sleep explicitly.
 > >>
 > >> Reported-by: Michael Ellerman <mpe@ellerman.id.au>
 > >> Reported-by: Dave Jones <davej@codemonkey.org.uk>
 > >> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
 > > 
 > > Thanks, this is working for me.
 > > 
 > > Tested-by: Michael Ellerman <mpe@ellerman.id.au>
 > > 
 > 
 > Steve,
 > 
 > Do you want to make a call on which one you want me to take it
 > through between these two patches - one from Dave and the other
 > from Namhyung Kim.
 > 
 > Please send me the patch I have to pull in. Namhyung Kim's patch
 > isn't in the format I can apply and I don't have Dave's patch in
 > my inbox.

Removing it entirely sounds like a much better choice, so I'd
wait for Namhyung to resend.

	Dave


  reply	other threads:[~2015-03-05 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 16:19 [PATCH] Remove redhat'ism from ftrace selftests Dave Jones
2015-02-24 18:18 ` Steven Rostedt
2015-02-24 18:22   ` Shuah Khan
2015-02-24 18:24     ` Dave Jones
2015-02-28  3:16       ` Namhyung Kim
2015-03-04  0:05         ` Shuah Khan
2015-03-04 10:47           ` Michael Ellerman
2015-03-04 12:44             ` Namhyung Kim
2015-03-05  1:18               ` Michael Ellerman
2015-03-05 15:14                 ` Shuah Khan
2015-03-05 15:17                   ` Dave Jones [this message]
2015-03-05 15:26                     ` Steven Rostedt
2015-03-05 15:24               ` Steven Rostedt

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=20150305151704.GA24554@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuahkh@osg.samsung.com \
    /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