>-----Original Message----- >From: [email protected] >[mailto:[email protected]] On >Behalf Of Mike Frysinger >Sent: Thursday, February 17, 2011 11:26 PM >To: [email protected] >Cc: [email protected] >Subject: Re: [Linux-kernel-commits] [9620] >trunk/arch/blackfin/mach-bf561/include/mach/icc.h: >[!no_src_qa!][ #4788] bf561 inter-core communication driver: >add arch specific icc.h > >On Thu, Feb 17, 2011 at 05:16, ><[email protected]> wrote: >> Added: trunk/arch/blackfin/mach-bf561/include/mach/icc.h (0 => 9620) >> >> +typedef unsigned char sm_unit_t; >> +typedef unsigned short sm_uint16_t; >> +typedef unsigned long sm_uint32_t; >> +typedef sm_uint32_t sm_address_t; > >what exactly is wrong with existing standard C types >(uintXX_t) ? why must you declare your own arbitrarily named types ? >-mike
The ICC protocol is designed to be architecture, OS and Language indepenant. These protocol specific types are only used when access the data in message pipes. Sonic >_______________________________________________ >Linux-kernel-commits mailing list >[email protected] >https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits > _______________________________________________ Linux-kernel-commits mailing list [email protected] https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
