Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c

On Sun, Aug 20, 2006 at 08:36:00PM +0200, Eric Sesterhenn / Snakebyte wrote:
 > * Richard Knutsson ([email protected]) wrote:
 > > Eric Sesterhenn wrote:
 > hi,
 > 
 > > Would it not be preferable to use a 's32' instead of an 'int'? After 
 > > all, it seem 'val' needs to be 32 bits.
 > 
 > not sure, but wouldnt this collide with platforms where an int is 64
 > Bits?

None of the 64-bit Linux ports use ILP64.

		Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c
  - From: Eric Sesterhenn <[email protected]>

References:
- [Patch] Signedness issue in drivers/net/phy/phy_device.c
  - From: Eric Sesterhenn <[email protected]>
- Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c
  - From: Richard Knutsson <[email protected]>
- Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c
  - From: Eric Sesterhenn / Snakebyte <[email protected]>

Prev by Date: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
Next by Date: Re: [PATCH] set*uid() must not fail-and-return on OOM/rlimits
Previous by thread: Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c
Next by thread: Re: [Patch] Signedness issue in drivers/net/phy/phy_device.c
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]