[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A4B5213.9060003@monstr.eu>
Date: Wed, 01 Jul 2009 14:09:55 +0200
From: Michal Simek <monstr@...str.eu>
To: microblaze-uclinux@...e.uq.edu.au
CC: LKML <linux-kernel@...r.kernel.org>,
Remis Lima Baima <remis.developer@...glemail.com>
Subject: Re: [microblaze-uclinux] [PATCH 03/11] microblaze: fall back on generic
header files for the ABI
Arnd Bergmann wrote:
> On Wednesday 01 July 2009, Michal Simek wrote:
>> Added to next branch for test.
>>
>> I had to do one change.
>> Microblaze needs __kernel_mode_t as short.
>
> Can you explain why that is needed? Should I change the default in the generic file?
I did this change because of problem with inconsistency between kernel/glibc.
Current our glibc ipc_perm struct - mode is short - that's why I have setup kernel_mode_t to short too.
/* Data structure used to pass permission information to IPC operations. */
struct ipc_perm
{
__key_t __key; /* Key. */
__uid_t uid; /* Owner's user ID. */
__gid_t gid; /* Owner's group ID. */
__uid_t cuid; /* Creator's user ID. */
__gid_t cgid; /* Creator's group ID. */
unsigned short int mode; /* Read/write permission. */
unsigned short int __seq; /* Sequence number. */
unsigned short int __pad1;
unsigned long int __unused1;
unsigned long int __unused2;
};
Does it make more sense to define it as int?
Michal
>
>> + I removed __kernel_size_t and I'll recompile toolchain
>> for removing warning messages
>
> Ah, good.
>
> Arnd <><
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@...e.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists