kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: me@sillymon.ch (Silvan Jegen)
To: kernelnewbies@lists.kernelnewbies.org
Subject: single, comprehensive kernel data types document?
Date: Fri, 15 Apr 2016 15:08:14 +0200	[thread overview]
Message-ID: <0c47f7ea75ba44f3a1fb8835a3df7de8@sillymon.ch> (raw)
In-Reply-To: <3e0913de8af67a2489ffa472ea0186f0@mail.vivaldi.net>

Am 2016-04-15 14:37, schrieb John Chludzinski:
> Never use stdint.h? Wasn't that the intent of stdint.h ... for kernel
> code? For embedded code?

I could be wrong about this but the reason for not using it may be that 
there is no standard C library where the Kernel lives. Thus using types 
from stdint.h would be confusing. Also, the string "u16" is much shorter 
than "uint16_t" and thus must surely be faster! :P


Cheers,

Silvan

  reply	other threads:[~2016-04-15 13:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 12:04 single, comprehensive kernel data types document? Robert P. J. Day
2016-04-15 12:27 ` Greg KH
2016-04-15 12:37   ` John Chludzinski
2016-04-15 13:08     ` Silvan Jegen [this message]
2016-04-15 13:09     ` Daniel.
2016-04-15 13:55       ` Greg KH
2016-04-15 16:28         ` Daniel.
2016-04-15 13:53     ` Greg KH
2016-04-15 15:59   ` Nicholas Mc Guire
2016-04-15 16:18     ` Greg KH
2016-04-15 17:07       ` Valdis.Kletnieks at vt.edu
2016-04-15 20:15         ` Greg KH
2016-04-20 20:37           ` Rob Groner
2016-04-21  2:51             ` Greg KH
2016-04-21 12:51               ` Rob Groner
2016-04-21 19:34                 ` Josh Cartwright
2016-04-22  2:37                 ` Greg KH
2016-04-22  3:02                   ` Valdis.Kletnieks at vt.edu
2016-04-22  3:13                     ` Greg KH

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=0c47f7ea75ba44f3a1fb8835a3df7de8@sillymon.ch \
    --to=me@sillymon.ch \
    --cc=kernelnewbies@lists.kernelnewbies.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).