From: Bernd Jendrissek <berndj@prism.co.za>
To: Andrew Hendry <ahendry@tusc.com.au>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>,
eis@baty.hanse.de, linux-x25@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] X25: Add ITU-T facilites
Date: Thu, 20 Oct 2005 09:41:29 +0200 [thread overview]
Message-ID: <20051020074129.GA13695@prism.co.za> (raw)
In-Reply-To: <1129770654.3574.1154.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Oct 20, 2005 at 11:10:54AM +1000, Andrew Hendry wrote:
> __u32 or unsigned int look to be the norm for other similar headers,
> whats the recommended type of types to be used?
Dunno if this helps, but AFAIK the C language (as of 1999 or is it 2000)
blesses uint32_t and friends.
Indeed, <linux/types.h> (in the kernel source tree) defines these
*standard* sized types.
HTH
- --
A PC without Windows is like ice cream without ketchup.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Please fetch my new key 804177F8 from hkp://wwwkeys.eu.pgp.net/
iD8DBQFDV0ohwyMv24BBd/gRAnOAAKCpTJLsIIQCGW4X/KMyoIMwZ0TNewCff2vE
IO7gmOpr1zuFa515lmIPWno=
=uytG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-10-20 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1129513666.3747.50.camel@localhost.localdomain>
[not found] ` <20051017022826.GA23167@mandriva.com>
2005-10-18 6:09 ` [PATCH] X25: Add ITU-T facilites Andrew Hendry
2005-10-18 6:23 ` YOSHIFUJI Hideaki / 吉藤英明
2005-10-18 15:37 ` Arnaldo Carvalho de Melo
2005-10-18 15:48 ` linux-os (Dick Johnson)
2005-10-20 1:10 ` Andrew Hendry
2005-10-20 7:41 ` Bernd Jendrissek [this message]
2005-10-20 12:30 ` Arnd Bergmann
2005-10-24 1:01 ` Andrew Hendry
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=20051020074129.GA13695@prism.co.za \
--to=berndj@prism.co.za \
--cc=acme@ghostprotocols.net \
--cc=ahendry@tusc.com.au \
--cc=eis@baty.hanse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).