[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080713142317.97111c81.akpm@linux-foundation.org>
Date: Sun, 13 Jul 2008 14:23:17 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Brownell <david-b@...bell.net>
Cc: Dmitry Baryshkov <dbaryshkov@...il.com>,
linux-kernel@...r.kernel.org,
Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
Russell King <rmk+lkml@....linux.org.uk>,
Paul Mundt <lethal@...ux-sh.org>,
pHilipp Zabel <philipp.zabel@...il.com>,
Pavel Machek <pavel@....cz>, tony@...mide.com, paul@...an.com,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
ian <spyro@....com>
Subject: Re: [PATCH 1/3] genclk: add generic framework for managing clocks.
On Sun, 13 Jul 2008 14:12:32 -0700 David Brownell <david-b@...bell.net> wrote:
> On Saturday 12 July 2008, Andrew Morton wrote:
> > > +EXPORT_SYMBOL(clk_get_parent);
> >
> > As this is a new kernel-wide utility library, it is appropriate that
> > all of its public interfaces (at least) be documented. __An appropriate
> > way of doing that is via kerneldoc annotation. __Please don't forget to
> > document return values and call environment prerequisites (eg: requires
> > foo_lock, may be called from interrupt context, etc, etc).
>
> That is, the stuff that's not already documented in <linux/clk.h>;
> that's where clk_get_parent() is documented, for example.
argh. That's why I missed it - please don't document stuff in header
files. The usual approach is to document interfaces at the
implementation site.
Except for structs where of course there is no choice. But then,
the .h file _is_ the definition site.
--
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