From: "Liu, Changcheng" <changcheng.liu@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: broonie@opensource.wolfsonmicro.com, mingo@redhat.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] ASoC: trace: track dapm type in snd_soc_dapm_widget
Date: Wed, 8 Aug 2018 20:59:21 +0800 [thread overview]
Message-ID: <20180808125921.GA145678@sofia> (raw)
In-Reply-To: <20180808085301.2b0617c6@gandalf.local.home>
Thanks Steven for the suggestion.
I'll write two patches. One is for cleaning the format issue. The other
is for tracking the dapm up/down sequence in trace events.
B.R.
Changcheng
On 08:53 Wed 08 Aug, Steven Rostedt wrote:
> On Wed, 8 Aug 2018 20:39:22 +0800
> "Liu, Changcheng" <changcheng.liu@intel.com> wrote:
>
> > > > - TP_printk("widget=%s val=%d", __get_str(name),
> > > > - (int)__entry->val)
> > > > + TP_printk("widget=%s dapm_id=%d val=%d", __get_str(name),
> > > > + (int)__entry->id, (int)__entry->val)
> > >
> > > Not sure why it was there before, but the (int) typecast isn't needed
> > > in either case. __field(int, val) makes __entry->val of type int. Same
> > > for id.
> > >
> > > -- Steve
> >
> > @Steve: This patch aims at tracking the dapm up/down sequence. For the
> > (int) typecast format problem, what do you think of using another
> > seperate patch to resolve it?
>
> Yeah, I was just commenting on that as a general comment. It doesn't
> affect the actual patch, which I don't see anything wrong with it from
> a tracing point of view.
>
> I agree the typecast removal should be done in a separate clean-up
> patch.
>
> -- Steve
prev parent reply other threads:[~2018-08-08 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 9:29 [PATCH] ASoC: trace: track dapm type in snd_soc_dapm_widget Liu, Changcheng
2018-08-08 12:24 ` Steven Rostedt
2018-08-08 12:39 ` Liu, Changcheng
2018-08-08 12:53 ` Steven Rostedt
2018-08-08 12:59 ` Liu, Changcheng [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=20180808125921.GA145678@sofia \
--to=changcheng.liu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.