linux-kernel - Re: [PATCH] ASoC: trace: track dapm type in snd_soc_dapm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180808125921.GA145678@sofia>
Date:   Wed, 8 Aug 2018 20:59:21 +0800
From:   "Liu, Changcheng" <changcheng.liu@...el.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     broonie@...nsource.wolfsonmicro.com, mingo@...hat.com,
        linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH] ASoC: trace: track dapm type in snd_soc_dapm_widget

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@...el.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