mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] tools lib traceevent: Clean up format of args in cfg80211 plugin
Date: Mon, 16 Jun 2014 11:11:17 +0200	[thread overview]
Message-ID: <20140616091117.GB8312@krava.brq.redhat.com> (raw)
In-Reply-To: <20140612194420.24073744@gandalf.local.home>

On Thu, Jun 12, 2014 at 07:44:20PM -0400, Steven Rostedt wrote:
> While synchronizing what's in trace-cmd vs what's in perf, I came
> across a change that was made when entering the cfg80211 plugin into
> the tools/lib/traceevent directory. The function prototype went from:
> 
> static unsigned long long process___le16_to_cpup(struct trace_seq *s,
> 						 unsigned long long *args)
> 
> to:
> 
> static unsigned long long
> process___le16_to_cpup(struct trace_seq *s,
> 		       unsigned long long *args)
> 
> I can understand the line break after the long long, but there's no
> reason to keep args on a separate line.
> 
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

queued, thanks

jirka

> ---
> diff --git a/tools/lib/traceevent/plugin_cfg80211.c b/tools/lib/traceevent/plugin_cfg80211.c
> index c066b25..4592d84 100644
> --- a/tools/lib/traceevent/plugin_cfg80211.c
> +++ b/tools/lib/traceevent/plugin_cfg80211.c
> @@ -5,8 +5,7 @@
>  #include "event-parse.h"
>  
>  static unsigned long long
> -process___le16_to_cpup(struct trace_seq *s,
> -		       unsigned long long *args)
> +process___le16_to_cpup(struct trace_seq *s, unsigned long long *args)
>  {
>  	uint16_t *val = (uint16_t *) (unsigned long) args[0];
>  	return val ? (long long) le16toh(*val) : 0;

  reply	other threads:[~2014-06-16  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 23:44 Steven Rostedt
2014-06-16  9:11 ` Jiri Olsa [this message]
2014-06-25  5:49 ` [tip:perf/core] " tip-bot for 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=20140616091117.GB8312@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --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

all inboxes | Powered by JetHome®