From: Rene Herman <rene.herman@keyaccess.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] PNP: make the resource type an unsigned long
Date: Sat, 09 Aug 2008 07:32:25 +0200 [thread overview]
Message-ID: <489D2BE9.4070206@keyaccess.nl> (raw)
In-Reply-To: <489D2A2F.7060206@zytor.com>
On 09-08-08 07:25, H. Peter Anvin wrote:
>>> Seems a bit pointless ... either one of those flags is >= 32 bits, in
>>> which case we need u64, or it's not, in which case there is no reason
>>> to burden the output with bits we don't need.
>>
>> Yes, it's a not a functional patch -- only a type-consistency one.
>> Right now we're mixing ints (signed ones even) and unsigned longs and
>> while in this case that's not a functional problem it's messy and
>> inconsistent.
>>
>> I agree (as Andrew said earlier as well) that the struct resource
>> flags member should probably just be a u32 but it's not. Changing that
>> would be a bigger change than just a simple conistency thing.
>>
>
> You're going in the wrong direction for consistency. long is different
> on 32 and 64 bits, and really should be avoided unless that is intended.
I know and fair enough but changing struct resource is just a bit too
central for my tastes.
<shrug>
Rene.
next prev parent reply other threads:[~2008-08-09 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 6:39 [PATCH] PNP: make the resource type an unsigned long Rene Herman
2008-08-08 21:55 ` H. Peter Anvin
2008-08-09 5:21 ` Rene Herman
2008-08-09 5:25 ` H. Peter Anvin
2008-08-09 5:32 ` Rene Herman [this message]
2008-08-11 21:59 ` Bjorn Helgaas
2008-08-11 22:08 ` H. Peter Anvin
2008-08-11 22:18 ` Bjorn Helgaas
2008-08-12 4:15 ` Rene Herman
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=489D2BE9.4070206@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=hpa@zytor.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 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.