From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44C78A48.4000508@domain.hid> Date: Wed, 26 Jul 2006 17:29:12 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-help] How can I now when it will be next periodic task release point? References: <200607251735.35500.lbocseg@domain.hid> <44C6929C.5030804@domain.hid> <44C78720.7040904@domain.hid> In-Reply-To: <44C78720.7040904@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE8EFB34F740587D13146956F" Sender: jan.kiszka@domain.hid List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rodrigo Rosenfeld Rosas Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE8EFB34F740587D13146956F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Rodrigo Rosenfeld Rosas wrote: > Jan Kiszka escreveu: >> See my attached patch. It should fix rt_task_inquire in a way that mee= ts >> your requirements. It also clarifies the doc. Only compile tested. >> =20 > Thank you Jan. > Anyway, I couldn't find the modifications to clarify the doc. It > clarified the comment inside the header but RT_TASK_INFO is not > documented yet from the html documentation generated by Doxygen (at > least I couldn't find it). Well, true. Don't know ATM what prevents such structures being included in the Doxygen run, but this should be fixed in my eyes. Probably it's "just" about adding the related header parts to the right Doxygen group. Any volunteers around? Jan --------------enigE8EFB34F740587D13146956F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEx4pIniDOoMHTA+kRAlJSAJ9l/ITsrAJb4cgAc8sW3q1/F4wmCQCfQSPR 0JQlABRXcjqlimpBwtSlb8A= =6nDw -----END PGP SIGNATURE----- --------------enigE8EFB34F740587D13146956F--