[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1307967287.9218.64.camel@gandalf.stny.rr.com>
Date: Mon, 13 Jun 2011 08:14:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Frederic Weisbecker <fweisbec@...il.com>,
yrl.pp-manager.tt@...achi.com,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Namhyung Kim <namhyung@...il.com>
Subject: Re: [PATCH 15/15] tracing/kprobes: Fix kprobe-tracer to support
stack trace
On Mon, 2011-06-13 at 13:50 +0200, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > > > + __ftrace_trace_stack(global_trace.buffer, flags, 3, preempt_count(),
> > > > + NULL);
> > >
> > > pointless linebreak.
> >
> > Again, probably to do with the 80 char limit.
>
> Well, the point of the 80 char limit warning these days is to force a
> cleanup of the code. Breaking the line mindlessly *uglifies* the code
> so it's pointless to do it.
>
> In terms of terminal readability line length up to 90-100 cols is
> acceptable for code that is otherwise not ugly.
I totally agree. I've just had arguments with others that are more 80
character nazi than I am. ;)
-- 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