linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: matthias@kaehlcke.net (Matthias Kaehlcke)
To: linux-arm-kernel@lists.infradead.org
Subject: Use of data types
Date: Mon, 18 Jan 2010 14:42:15 +0100	[thread overview]
Message-ID: <20100118134215.GB16182@darwin> (raw)
In-Reply-To: <20100118134120.GB31345@pengutronix.de>

El Mon, Jan 18, 2010 at 02:41:20PM +0100 Uwe Kleine-K?nig ha dit:

> On Mon, Jan 18, 2010 at 09:43:12PM +0900, Khushhua Mogambo wrote:
> > Hi
> >   I starting to port Linux kernel to my companies new ARM based
> > SoC and development board.
> > 
> > Some of the regs is 16bits wide and some is 32bits width. I ask if
> > my using u16 and u32 in place of 'unsigned short' and 'unsigned int'
> > in the whole porting would be acceptable or not?
> > 
> > In different wording, using only u16 and u32 always is considered good
> > quality or bad?
> I prefer using u32 over int.  Still more if your register space isn't uniform.

ditto

how about using the C99 types uint32_t, ... in the kernel? 

-- 
Matthias Kaehlcke
Embedded Linux Developer
Barcelona

              Insanity: doing the same thing over and over
                again and expecting different results
                            (Albert Einstein)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

  reply	other threads:[~2010-01-18 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 12:43 Use of data types Khushhua Mogambo
2010-01-18 13:41 ` Uwe Kleine-König
2010-01-18 13:42   ` Matthias Kaehlcke [this message]
2010-01-18 13:52     ` Russell King - ARM Linux
     [not found]     ` <4B546900.3020506@ru.mvista.com>
2010-01-19 11:57       ` Khushhua Mogambo
2010-01-19 17:42         ` Russell King - ARM Linux
2010-01-20 12:15           ` Khushhua Mogambo
2010-01-20  5:25         ` Ben Dooks
2010-01-18 13:48   ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100118134215.GB16182@darwin \
    --to=matthias@kaehlcke.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).