[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130905155217.03df4d45@gandalf.local.home>
Date: Thu, 5 Sep 2013 15:52:17 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Jiri Olsa <jolsa@...hat.com>
Subject: Re: [RFC][PATCH 14/18 v2] ftrace/lockdep: Have the RCU lockdep
splat show what function triggered
On Thu, 5 Sep 2013 21:18:39 +0200
Peter Zijlstra <peterz@...radead.org> wrote:
> On Sat, Aug 31, 2013 at 01:11:31AM -0400, Steven Rostedt wrote:
> > +void print_ftrace_rcu_func(int cpu)
> > +{
> > + unsigned long ip = per_cpu(ftrace_rcu_func, cpu);
> > +
> > + if (ip)
> > + printk("ftrace_rcu_func: %pS\n",
> > + (void *)per_cpu(ftrace_rcu_func, cpu));
> > +}
>
> That's missing { }.
Hmm, that's an interesting point. Why the { } because I break up the
printk for the 80 character limit?
Although, I'm still not convinced that it needs { }, as it looks to me
that it flows nicely without it. I can't find a place in CodingStyle
that says { } are needed here.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists