From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Questions about scsi.c
Date: Thu, 25 Oct 2007 13:25:37 -0500 [thread overview]
Message-ID: <200710251325.37586.rob@landley.net> (raw)
In-Reply-To: <20071025084039.971383af.rdunlap@xenotime.net>
On Thursday 25 October 2007 10:40:39 am Randy Dunlap wrote:
> On Thu, 25 Oct 2007 06:06:03 -0500 Rob Landley wrote:
> > The rest sort of seems to make sense, although the kerneldoc comments in
> > include/scsi/scsi_device.h are before #defines instead of before function
> > definitions so the make xmldocs infrastructure (something in either
> > scripts/basic/docproc.c or scripts/kernel-doc) skips right over it
> > because it can't figure out the argument types. Separate issue, todo
> > item for later...
>
> scripts/kernel-doc is supposed to (and usually does) handle
> kernel-doc notation of a #define macro. Are these 2 not working?
Not when I tried it.
> $ make xmldocs
> make -C /home/landley/linux/hg O=/home/landley/linux/temp xmldocs
> DOCPROC Documentation/DocBook/scsi_midlayer.xml
> Warning(/home/landley/linux/hg//include/scsi/scsi_device.h): no structured
> comments found
Entirely possible I'm doing something wrong:
<sect1 id="scsi_device.h">
<title>include/scsi/scsi_device.h</title>
<para>
</para>
!Einclude/scsi/scsi_device.h
</sect1>
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-10-25 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 11:06 Questions about scsi.c Rob Landley
2007-10-25 15:40 ` Randy Dunlap
2007-10-25 18:25 ` Rob Landley [this message]
2007-10-25 17:32 ` Randy Dunlap
2007-10-25 19:30 ` Rob Landley
2007-10-25 21:40 ` Rob Landley
2007-10-25 20:49 ` Randy Dunlap
2007-10-25 23:13 ` Rob Landley
2007-10-30 12:34 ` Jeff Garzik
2007-10-30 14:43 ` James Bottomley
2007-10-30 22:23 ` Rob Landley
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=200710251325.37586.rob@landley.net \
--to=rob@landley.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.