From: Randy Dunlap <randy.dunlap@oracle.com>
To: Doug Maxey <dwm@enoyolf.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: kernel doc / docbook pdfdocs question
Date: Thu, 1 Oct 2009 08:57:07 -0700 [thread overview]
Message-ID: <20091001085707.d74e3e79.randy.dunlap@oracle.com> (raw)
In-Reply-To: <27289.1254375747@jerryjeff.riw.enoyolf.org>
On Thu, 01 Oct 2009 00:42:27 -0500 Doug Maxey wrote:
>
> On Wed, 30 Sep 2009 17:30:02 PDT, Stephen Hemminger wrote:
> >On Wed, 30 Sep 2009 14:59:36 -0500
> >Doug Maxey <dwm@enoyolf.org> wrote:
> >
> >>
> >> Randy,
> >>
> >> This may be slightly off topic for this list, but it does involve an
> >> (as yet un-released) network driver. :)
> >>
> >> Do you have any insight that could guide me toward a fix for an issue
> >> seen with some header file constructs when trying to generate a pdf
> >> docbook?
> >>
> >
> >Why clutter docbook output (which is supposed to be about general kernel
> >API's) with output for data structures in one driver.
>
> It would be a general mechanism, and it would be to document an API.
> There are other subsystems that use DECLARE_BITMAP() (e.g., scsi).
> Just none at the moment that attempt to describe such a member,
> possibly because there isn't a way to document it. Dunno. Build it
> and they will come. There is one party that is interested anyway.
>
> Finally did find where this was getting warned about / tossed, in
> kernel-doc itself. =)
Hi,
Sorry for the delayed reply. I was away yesterday.
What did you find in kernel-doc? Something like the
"cannot understand prototype" message or something else?
Features/support in kernel-doc is mostly added on an as-needed basis.
Now that you have provided a sample, I can try to add support for it,
but it's not exactly a high priority for me... or you can add support
for it to kernel-doc and send a patch for it. :)
---
~Randy
prev parent reply other threads:[~2009-10-01 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 19:59 kernel doc / docbook pdfdocs question Doug Maxey
2009-10-01 0:30 ` Stephen Hemminger
2009-10-01 5:42 ` Doug Maxey
2009-10-01 15:57 ` Randy Dunlap [this message]
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=20091001085707.d74e3e79.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dwm@enoyolf.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).