From: Randy Dunlap <rdunlap@xenotime.net>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: KML <linux-kernel@vger.kernel.org>
Subject: Re: make htmldocs errors
Date: Tue, 22 Jul 2008 20:23:36 -0700 [thread overview]
Message-ID: <20080722202336.f056a5fe.rdunlap@xenotime.net> (raw)
In-Reply-To: <804dabb00807221948y1317633exc1a2009540b23239@mail.gmail.com>
On Wed, 23 Jul 2008 10:48:52 +0800 Peter Teoh wrote:
> Thank you Randy for the explanation.
>
> Just for your interest, other tree like tracing/for-linus at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
AFAIAC, one person cannot fix _all_ git trees. There are at least
200 kernel git trees at git.kernel.org (probably lots of them are defunct).
It just doesn't scale IMHO, so please send patches after you confirm that
patches are indeed needed.
> has somewhat similar problem too (but different files altogether)...
>
> /sda3/ftrace/tracing/for-linus>make htmldocs
> DOCPROC Documentation/DocBook/debugobjects.xml
> HTML Documentation/DocBook/debugobjects.html
> DOCPROC Documentation/DocBook/deviceiobook.xml
> HTML Documentation/DocBook/deviceiobook.html
> DOCPROC Documentation/DocBook/filesystems.xml
> HTML Documentation/DocBook/filesystems.html
> DOCPROC Documentation/DocBook/gadget.xml
> Error(/sda3/ftrace/tracing/for-linus//drivers/usb/gadget/config.c:132):
> cannot understand prototype: 'struct usb_descriptor_header **__init
> usb_copy_descriptors(struct usb_descriptor_header **src) '
> Error(/sda3/ftrace/tracing/for-linus//drivers/usb/gadget/config.c:183):
> cannot understand prototype: 'struct usb_endpoint_descriptor *__init
> usb_find_endpoint( struct usb_descriptor_header **src, struct
> usb_descriptor_header **copy, struct usb_endpoint_descriptor *match
> ) '
Fix for above is in the kbuild tree and I have ask that it be merged Soon.
Otherwise I'll need to merge it separately.
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:129):
> No description found for parameter 'list'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'list'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'functions'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'next_interface_id'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'highspeed'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'fullspeed'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:226):
> No description found for parameter 'interface[MAX_CONFIG_INTERFACES]'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:322):
> No description found for parameter 'desc'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:322):
> No description found for parameter 'configs'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:322):
> No description found for parameter 'driver'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:322):
> No description found for parameter 'next_string_id'
> Warning(/sda3/ftrace/tracing/for-linus//include/linux/usb/composite.h:322):
> No description found for parameter 'lock'
I've already sent that list to the linux-usb mailing list...
I mainly try to focus on the fatal errors or changes that need to be made
to scripts/kernel-doc.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
next prev parent reply other threads:[~2008-07-23 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 11:07 Peter Teoh
2008-07-22 15:42 ` Randy Dunlap
2008-07-23 2:48 ` Peter Teoh
2008-07-23 3:23 ` Randy Dunlap [this message]
2008-11-05 16:25 Peter Teoh
2008-11-05 16:35 ` Randy Dunlap
2008-11-05 17:04 ` Randy Dunlap
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=20080722202336.f056a5fe.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=htmldeveloper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®