linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Denis Kirjanov <kda@linux-powerpc.org>
To: Steven Rostedt <rostedt@goodmis.org>,
	Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] powerpc: tracing: don't trace hcalls on offline CPUs
Date: Fri, 5 Feb 2016 17:48:57 +0300	[thread overview]
Message-ID: <CAOJe8K03+hPZx5Ov1r5WtyvgsJH3N1LV1wfYA6eBWa=qwiXrbA@mail.gmail.com> (raw)
In-Reply-To: <20160205093647.79ca2f70@gandalf.local.home>

On 2/5/16, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 5 Feb 2016 14:20:17 +0300
> Denis Kirjanov <kda@linux-powerpc.org> wrote:
>
>> >>> Signed-off-by: Denis Kirjanov <kda@linux-powerpc.org>
>> >
>> > Hi Steven,
>> >
>> > please apply with Michael's acked-by tag.
>>
>> ping
>>
>
> Actually, can you take this through the ppc tree? The
> TRACE_EVENT_FN_COND is already in mainline.
>
> You can add my:
>
> Acked-by: Steven Rostedt <rostedt@goodmis.org>

Hey Michael,

Please apply the patch.

Thanks!

>
> -- Steve
>

  reply	other threads:[~2016-02-05 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 20:18 [PATCH v3 1/2] tracing: introduce TRACE_EVENT_FN_COND macro Denis Kirjanov
2015-12-14 20:18 ` [PATCH v3 2/2] powerpc: tracing: don't trace hcalls on offline CPUs Denis Kirjanov
2015-12-23 16:12   ` Steven Rostedt
2016-01-12 10:53     ` Denis Kirjanov
2016-01-12 11:53   ` Michael Ellerman
2016-01-19 11:53     ` Denis Kirjanov
2016-02-05 11:20       ` Denis Kirjanov
2016-02-05 14:36         ` Steven Rostedt
2016-02-05 14:48           ` Denis Kirjanov [this message]
2016-02-09  9:24           ` Michael Ellerman
2016-02-09 12:16   ` [v3,2/2] " Michael Ellerman

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='CAOJe8K03+hPZx5Ov1r5WtyvgsJH3N1LV1wfYA6eBWa=qwiXrbA@mail.gmail.com' \
    --to=kda@linux-powerpc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).