From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Use of data types
Date: Tue, 19 Jan 2010 17:42:45 +0000 [thread overview]
Message-ID: <20100119174245.GA1886@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <2703439e1001190357r65a507d2v668bbfca1a07c176@mail.gmail.com>
On Tue, Jan 19, 2010 at 08:57:03PM +0900, Khushhua Mogambo wrote:
> from thread, i understand that u32 is encouraged whenever we have reason. I m
> going to use u8,16,32 heavily.
Incorrect.
As I said, use u8,u16,u32 when you need something that's of that size
(eg, for storing values from hardware registers.) If you don't require
something of a specific size, then don't use them.
next prev parent reply other threads:[~2010-01-19 17: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
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 [this message]
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=20100119174245.GA1886@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).