[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0906101511070.30552@gandalf.stny.rr.com>
Date: Wed, 10 Jun 2009 15:11:50 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Mike Frysinger <vapier.adi@...il.com>
cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] ftrace: document basic ftracer/ftracer graph needs
On Wed, 10 Jun 2009, Mike Frysinger wrote:
> On Wed, Jun 10, 2009 at 14:45, Steven Rostedt wrote:
> > On Wed, 10 Jun 2009, Mike Frysinger wrote:
> >> there should be at least tips in each HAVE_XXX as to where to look for
> >> implementation details.
> >
> > That can be opening a can of worms.
>
> no it isnt:
> config HAVE_FUNCTION_TRACER
> bool
> help
> Please see Documentation/trace/ftrace-implementation.txt
I'm fine with that, I was thing something else.
>
> > Really, the focus of the documentation in Kconfig is about why things must
> > be selected, not how to implement the code to add that selection.
>
> except that some of these defines come from the exact implementation details.
>
> > If there's a HAVE_XXX in Kconfig that I want to see how to implement it, I
> > go off and do 'grep -r XXX Documentation'.
>
> i look for the source of the define because ive given up on the
> Documentation actually being relevant
And you think documentation in Kconfig will be updated??
-- 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