Prev: shutdown bugs, since about 2.6.31 or so
Next: timer: Provide config option for enabling timer tracepoints
From: Johannes Berg on 22 Mar 2010 21:20
On Tue, 2010-03-23 at 01:32 +0100, Jan Kara wrote:
> CC: linux-wireless(a)vger.kernel.org
> Signed-off-by: Jan Kara <jack(a)suse.cz>

You kinda missed something there, this patch doesn't explain to me why
and it's all I ever got to see :)

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Steven Rostedt on 23 Mar 2010 20:00
On Mon, 2010-03-22 at 18:11 -0700, Johannes Berg wrote:
> On Tue, 2010-03-23 at 01:32 +0100, Jan Kara wrote:
> > CC: linux-wireless(a)vger.kernel.org
> > Signed-off-by: Jan Kara <jack(a)suse.cz>
>
> You kinda missed something there, this patch doesn't explain to me why
> and it's all I ever got to see :)

This patch set is about fine grained tuning of what tracepoints get
enabled and which don't. I honestly think that this should only be
permitted if CONFIG_EMBEDDED is set (if it should be permitted at all).

I would much rather find a way to lower the tracepoint footprint than to
pick and choose what tracepoints get enabled.

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: shutdown bugs, since about 2.6.31 or so
Next: timer: Provide config option for enabling timer tracepoints