public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@uk.sistina.com>
To: dm-devel@sistina.com
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [dm-devel] Re: [RFC] device-mapper ioctl interface
Date: Fri, 6 Jun 2003 20:53:08 +0100	[thread overview]
Message-ID: <20030606205308.B12727@uk.sistina.com> (raw)
In-Reply-To: <20030606171700.GC12231@kroah.com>; from greg@kroah.com on Fri, Jun 06, 2003 at 10:17:00AM -0700

On Fri, Jun 06, 2003 at 10:17:00AM -0700, Greg KH wrote:
> Minor comment:
> 	- please do not use uint_32t types in kernel header files.  Use
> 	  the proper __u32 type which is guarenteed to be the proper
> 	  size across the user/kernel boundry.

So is uint32_t:

    linux/types.h: typedef         __u32           uint32_t;

I think this comment is about style conformity i.e. most linux kernel
developers avoid these (not-so-)new and more-portable C99 types.

Alasdair
-- 
agk@uk.sistina.com

Refs. http://www.xml.com/ldd/chapter/book/ch10.html
      http://www.unix-systems.org/whitepapers/64bit.html

  reply	other threads:[~2003-06-06 19:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-05  9:39 [RFC] device-mapper ioctl interface Joe Thornber
2003-06-05 16:47 ` Kevin Corry
2003-06-05 17:00   ` [dm-devel] " Daniel Phillips
2003-06-05 17:50     ` Kevin Corry
2003-06-05 18:53       ` Daniel Phillips
2003-06-05 19:41   ` Joe Thornber
2003-06-06 16:11     ` Kevin Corry
2003-06-06 17:17 ` Greg KH
2003-06-06 19:53   ` Alasdair G Kergon [this message]
2003-06-09 20:03   ` [dm-devel] " Daniel Phillips
2003-06-09 20:39     ` Greg KH
2003-06-09 21:39       ` Daniel Phillips
2003-06-09 22:08   ` Daniel Phillips

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=20030606205308.B12727@uk.sistina.com \
    --to=agk@uk.sistina.com \
    --cc=dm-devel@sistina.com \
    --cc=linux-kernel@vger.kernel.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