[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090812105106.GA7885@elte.hu>
Date: Wed, 12 Aug 2009 12:51:06 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Alan Stern <stern@...land.harvard.edu>,
Andrew Morton <akpm@...ux-foundation.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Kernel development list <linux-kernel@...r.kernel.org>,
Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: [PATCH] Add kerneldoc for flush_scheduled_work()
* Peter Zijlstra <peterz@...radead.org> wrote:
> On Wed, 2009-08-12 at 11:41 +0200, Ingo Molnar wrote:
> > * Alan Stern <stern@...land.harvard.edu> wrote:
> >
> > > This patch (as1279) adds kerneldoc for flush_scheduled_work()
> > > containing a stern warning that the function should be avoided.
> > >
> > > Signed-off-by: Alan Stern <stern@...land.harvard.edu>
>
> > >
> > > +/**
> > > + * flush_scheduled_work - ensure that all work scheduled on keventd_wq has run to completion.
>
> > > + */
> >
> > Looks good - a small nit: please use proper/consistent line length,
> > something like:
> >
> > /**
> > * flush_scheduled_work - ensure that all work scheduled on
> > * keventd_wq has run to completion
> > *
>
> > */
>
>
> And here I was thinking kerneldoc doesn't actually work
> like that, but perhaps Randy fixed it so the initial
> description can line-wrap?
Ah, the main changes i did were to the body, that is what
caught my eyes. If KernelDoc doesnt handle line-wrap in the
first line then that has to stay so. (and KernelDoc needs to
be fixed as well - it should result in better documentation,
not worse)
Ingo
--
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