linux-kernel - Re: [PATCH 1/3] x86: unify asm/io.h: IO_SPACE

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]

Date:	Thu, 29 Jan 2009 01:45:35 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] x86: unify asm/io.h: IO_SPACE_LIMIT

H. Peter Anvin wrote:
> Hi Jeremy,
>
> I applied patch #1 to tip:x86/cleanups, however, patch #2 and #3 are
> identical... did you mean to do something different here?
>
> Furthermore, please provide an actual description (and preferrably an
> Impact: line) with your patches.  In particular, when unifying code that
> is identical between 32 and 64 bits, please specify this in the
> description (e.g. "unified functions X and Y which were already
> identical between 32 and 64 bits"), so we know why there isn't a
> preceeding patch to remove the remaining differences.

Oops.  Here they are.  The order is:

x86-unify-io.h-virt-phys.patch
x86-unify-io.h-ioremap-proto.patch

    J


View attachment "x86-unify-io.h-virt-phys.patch" of type "text/plain" (6304 bytes)

View attachment "x86-unify-io.h-ioremap-proto.patch" of type "text/plain" (4429 bytes)