lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <24697997.78131194167504382.hqa02330@nifty.com>
Date:	Sun, 4 Nov 2007 18:11:44 +0900 (JST)
From:	Komuro <hqa02330@...ty.com>
To:	Olof Johansson <olof@...om.net>
Cc:	Christoph Hellwig <hch@....de>, Matthew Wilcox <matthew@....cx>,
	linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linuxppc-dev@...abs.org, Andrew Morton <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v2] pcmcia: Remove replace kio_addr_t with unsigned int everywhere


Hi, 

It should be "unsigned long" instead of "unsigned int".

64bit architecture uses 64bit-Memory-mapped-IO.



Best Regards
Komuro


>
>
>pcmcia: Remove replace kio_addr_t with unsigned int everywhere
>
>Remove kio_addr_t, and replace it with unsigned int. No known architecture
>needs more than 32 bits for IO addresses and ports and having a separate
>type for it is just messy.
>
>This goes on top of the patch switching the io_req_t members from ioaddr_t
>to unsigned int.
>
>
>Signed-off-by: Olof Johansson <olof@...om.net>
>
>---
>
>On Sun, Oct 28, 2007 at 03:10:34PM -0500, Olof Johansson wrote:
>
>> This goes on top of the patch switching the io_req_t members from ioaddr_t
>> to unsigned int.
>
>Crap, I had an old version of that patch as base in my local tree when I did
>these edits. Here's a proper version.
>
>-Olof
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ