Here is the fifth maintenance release for the v2.2.x branch. Short
log follows:
[nucleus]
* Fix period validity check when setting up the timer for
periodic timing mode.
[hal]
* ppc: Define special wrappers to get/put_user macros which
bypass th
Hi Philippe,Not sure you have noticed this typo or not:xenomai-2.2.5/ksrc/skins/posix/syscall.c2674: nt __pse51_call_not_available(struct task_struct *curr, struct pt_regs *regs)should be:
int __pse51_call_not_available(struct task_struct *curr, struct pt_regs *regs)
Regards,-YiOn 11/6/06, Philippe
On Tue, 2006-11-07 at 14:32 +0800, Li Yi (Adam) wrote:
> Hi Philippe,
>
> Not sure you have noticed this typo or not:
>
> xenomai-2.2.5/ksrc/skins/posix/syscall.c
>
> 2674: nt __pse51_call_not_available(struct task_struct *curr, struct
> pt_regs *regs)
>
> should be:
>
> int __pse51_call_not_a
Another typo in xenomai-2.2.5/ksrc/drivers/testing/timerbench.c:412: printk("%s: bad ioctl code (0x%x)\n", _ _FUNCTION_, request);should be:printk("%s: bad ioctl code (0x%x)\n", _ _FUNCTION_ _, request);
-YiOn 11/7/06, Philippe Gerum <[EMAIL PROTECTED]> wrote:
On Tue, 2006-11-07 at 14:32 +0800, Li
On Wed, 2006-11-08 at 16:53 +0800, Li Yi (Adam) wrote:
> Another typo in xenomai-2.2.5/ksrc/drivers/testing/timerbench.c:
>
> 412:
> printk("%s: bad ioctl code (0x%x)\n", _ _FUNCTION_, request);
> should be:
> printk("%s: bad ioctl code (0x%x)\n", _ _FUNCTION_ _, request);
>
Yeah, rainy day in
