[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <27289.1254375747@jerryjeff.riw.enoyolf.org>
Date: Thu, 01 Oct 2009 00:42:27 -0500
From: Doug Maxey <dwm@...yolf.org>
To: Stephen Hemminger <shemminger@...tta.com>
cc: Randy Dunlap <randy.dunlap@...cle.com>,
netdev <netdev@...r.kernel.org>
Subject: Re: kernel doc / docbook pdfdocs question
On Wed, 30 Sep 2009 17:30:02 PDT, Stephen Hemminger wrote:
>On Wed, 30 Sep 2009 14:59:36 -0500
>Doug Maxey <dwm@...yolf.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. =)
++doug
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists