From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: single, comprehensive kernel data types document?
Date: Fri, 15 Apr 2016 13:15:38 -0700 [thread overview]
Message-ID: <20160415201538.GA19579@kroah.com> (raw)
In-Reply-To: <16162.1460740039@turing-police.cc.vt.edu>
On Fri, Apr 15, 2016 at 01:07:19PM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Fri, 15 Apr 2016 09:18:32 -0700, Greg KH said:
>
> > Within the kernel, yes, you can use lots of different types for the same
> > "real" variable size, but you shouldn't, just use the well-known and
> > common types "u8" and you will be fine. Those other ones are there due
> > to code being brought in from all over the place, that's what happens
> > with a codebase of 20 million lines at times :)
>
> What's the current feeling on using typedefs to get more type safety?
typedefs are evil, never use them. No non-core-kernel developer should
EVER create a new typedef, except for a function pointer signature.
greg k-h
next prev parent reply other threads:[~2016-04-15 20:15 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
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 [this message]
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=20160415201538.GA19579@kroah.com \
--to=greg@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.