From: "J . A . Magallon" <jamagallon@able.es>
To: Tim Jansen <tim@tjansen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scripts/kernel-doc: support for structs, unions, enum, typedef and other stuff
Date: Wed, 26 Sep 2001 16:02:23 +0200 [thread overview]
Message-ID: <20010926160223.A2738@werewolf.able.es> (raw)
In-Reply-To: <15m3N5-223p5sC@fmrl01.sul.t-online.com>
In-Reply-To: <15m3N5-223p5sC@fmrl01.sul.t-online.com>; from tim@tjansen.de on Wed, Sep 26, 2001 at 03:22:04 +0200
On 20010926 Tim Jansen wrote:
>Hi...
>
>The attached patch for scripts/kernel-doc adds the following features:
>
>1. You can document structs, unions, enums and typedef like this:
>/**
> * enum driver_type - Describes the type of a driver
> * @DRIVER_TYPE_DEVICE: driver controls a device (like fd.o)
> * @DRIVER_TYPE_BUS: driver manages a bus (like usbcore.o)
> *
> * Some description.
> */
>enum driver_type {
> DRIVER_TYPE_DEVICE = 0,
> DRIVER_TYPE_BUS = 1,
>};
>
I suppose it is too late, but can be an idea for 2.5.
Why do not use doxygen, instead of rewriting it ?
Yes, it adds another package dependency for kernel sources, but only for
people that wants to rebuild docs instead of using shipped ones.
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.1 (Cooker) for i586
Linux werewolf 2.4.10-beo #1 SMP Tue Sep 25 23:38:05 CEST 2001 i686
next prev parent reply other threads:[~2001-09-26 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 1:22 [PATCH] scripts/kernel-doc: support for structs, unions, enum, typedef and other stuff Tim Jansen
2001-09-26 14:02 ` J . A . Magallon [this message]
2001-09-26 16:27 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010926160223.A2738@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@tjansen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.