Hi all,

I'm a bit confused as to the status of the type 'u32' in the kernel I
use (2.6.29.4).
u32 is used in thread_info.h, but types.h uses __u32.

Now, while googling I came across a recent patch -
{Mon Feb 09 2009 Chuck Ebbert <cebb...@xxxxxxxxxx> +- Fix type in header
so iptables will build. (#484679) }
Although not related, it's the same issue - the patch applies a change
from u32 to __u32.

Should I change the type u32 -> __u32 in thread_info.h  ???
I'm not comfortable with that because that's "stable" kernel source.

Or am I simply overlooking some runtime constant/defintion I should have
present...
I can't see why that would be, I've built various modules before, never
had an issue like this.. ?


For reference, this is the chain (module.h -> downwards) - that causes
the error :

In file included
from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/preempt.h:9,
              from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/spinlock.h:50,
                 from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/mmzone.h:7,
                 from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/gfp.h:4,
                 from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/kmod.h:22,
                 from 
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/module.h:13,
                     from ../my_foo.c:11:
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/thread_info.h:26:
 error: expected specifier-qualifier-list before 'u32'
/home/kris/buildroot-2009.05/toolchain_build_arm_nofpu/linux-2.6.29.4/include/linux/thread_info.h:39:
 error: expected specifier-qualifier-list before 'u64'


-- 
Best regards,
Kris



--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ

Reply via email to