From: Jan Kiszka <jan.kiszka@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] broken docs
Date: Wed, 18 Jan 2006 20:03:25 +0100 [thread overview]
Message-ID: <43CE90FD.6000508@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Hi,
I noticed that the doxygen API output is partly broken. Under the
nucleus and native skin modules most functions became variables. I
haven't looked at the source yet, but I guess it should be resolvable,
especially as the RTDM docs are fine. This mail is to file the issue,
maybe I will have a look later - /maybe/.
Moreover, I was lacking a reference to RT_MUTEX_INFO. Does this
structure just needs to be added to the correct doxygen group? I guess
there are other undocumented structures out there as well (RT_TASK_INFO,
...?).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next reply other threads:[~2006-01-18 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 19:03 Jan Kiszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-30 10:55 [Xenomai-core] broken docs ROSSIER Daniel
2006-01-30 12:17 ` Jan Kiszka
2006-01-30 12:40 ` Gilles Chanteperdrix
2006-01-30 12:59 ` Jan Kiszka
2006-02-04 12:24 ` Jan Kiszka
2006-02-05 13:06 ` Gilles Chanteperdrix
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=43CE90FD.6000508@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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 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.