[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150803083741.04bfb6ed@lwn.net>
Date: Mon, 3 Aug 2015 08:37:41 -0600
From: Jonathan Corbet <corbet@....net>
To: Daniel Vetter <daniel@...ll.ch>
Cc: Danilo Cesar Lemes de Paula <danilo.cesar@...labora.co.uk>,
linux-doc@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Stephan Mueller <smueller@...onox.de>,
Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
intel-gfx <intel-gfx@...ts.freedesktop.org>,
dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH] scripts/kernel-doc Allow struct arguments documentation
in struct body
On Mon, 3 Aug 2015 10:23:19 +0200
Daniel Vetter <daniel@...ll.ch> wrote:
> > I'm wondering if we need a kernel summit session on commenting
> > conventions, markdown-in-kerneldoc, etc? Maybe I'll stick a proposal out
> > there.
>
> Might be useful, but I'm not sure how many people really would actively
> work on improving the tooling. The only comment I've seen is to maybe use
> gtkdoc, but that would be a pain since it's slightly incompatible with
> kerneldoc.
The idea was to get a sense for what sort of improvements would be
useful, to begin with. But my attempt to start a discussion on the
kernel summit list appears to have hit the ground pretty hard; I guess
that means I have free rein :)
I expect I'll apply the struct-args doc patch in the fairly near future.
Then we'll see if others complain when patches using it start to show up,
but the feature itself shouldn't break anything. I'm *really* hoping to
take a hard look at Danilo's stuff for a 4.3 merge as well. It should be
possible, but there's real-world obnoxiousness that is doing its best to
get in the way.
jon
--
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