All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: arnd@arndb.de, Sam Ravnborg <sam@ravnborg.org>,
	Kyle McMartin <kyle@infradead.org>, Ingo Molnar <mingo@elte.hu>,
	Jaswinder Singh Rajput <jaswinderrajput@gmail.com>,
	mingo@redhat.com, dwmw2@infradead.org,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [patch 5/7] make netfilter use strict integer types
Date: Wed, 25 Feb 2009 16:24:38 -0800	[thread overview]
Message-ID: <49A5E146.4060208@zytor.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0902260104220.20789@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Thursday 2009-02-26 00:51, arnd@arndb.de wrote:
> 
>> Netfilter traditionally uses BSD integer types in its
>> interface headers. This changes it to use the Linux
>> strict integer types, like everyone else.
> 
> I _strongly disagree_ with this move. Userspace also has the uintX
> types via <stdint.h>/<cstdint>, and now you are adding a dependency
> on linux/types.h, not to mention that your step can lead to compile
> time piling up.
> 
> IMHO, __uXX should be replaced by uintX_t, but a move this great I
> will leave to future generations because there is just too much
> persisting opinions wrt. such proposal. As such I'd like to join
> and persist on my position and that uintX that we have should be kept.
> 
>> -	u_int8_t flags;
>> -	u_int8_t mask;
>> +	__u8 flags;
>> +	__u8 mask;

Not to mention the fact that the standard type is uint8_t, not u_int8_t 
as the file currently have, which makes it double broken.
	
	-hpa

  parent reply	other threads:[~2009-02-26  0:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 23:51 [patch 0/7] Use strict kernel types to fix the world arnd
2009-02-25 23:51 ` [patch 1/7] make exported headers use strict posix types arnd
2009-02-25 23:51 ` [patch 2/7] make most exported headers use strict integer types arnd
2009-02-25 23:51 ` [patch 3/7] make MTD " arnd
2009-02-26  0:32   ` Thiago Galesi
2009-02-26  0:34     ` Arnd Bergmann
2009-02-25 23:51 ` [patch 4/7] make drm " arnd
2009-02-25 23:51 ` [patch 5/7] make netfilter " arnd
2009-02-26  0:10   ` Jan Engelhardt
2009-02-26  0:14     ` H. Peter Anvin
2009-02-26  0:39       ` Jan Engelhardt
2009-02-26  1:02         ` H. Peter Anvin
2009-02-26  0:24     ` H. Peter Anvin [this message]
2009-02-26  0:55     ` David Miller
2009-02-26  0:58       ` H. Peter Anvin
2009-02-26  0:59         ` David Miller
2009-02-25 23:51 ` [patch 6/7] coda_psdev: dont export internals to user space arnd
2009-02-25 23:51 ` [patch 7/7] remove __KERNEL_STRICT_NAMES arnd
2009-02-26  0:02 ` [patch 0/7] Use strict kernel types to fix the world H. Peter Anvin
2009-02-26  0:24   ` Arnd Bergmann
2009-02-26  0:30     ` H. Peter Anvin
2009-02-26  0:52       ` Arnd Bergmann
2009-02-26  0:56         ` Ingo Molnar

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=49A5E146.4060208@zytor.com \
    --to=hpa@zytor.com \
    --cc=arnd@arndb.de \
    --cc=coreteam@netfilter.org \
    --cc=dwmw2@infradead.org \
    --cc=jaswinderrajput@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=kyle@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sam@ravnborg.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.