summaryrefslogtreecommitdiffstats
path: root/include/asm-powerpc/grackle.h
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2007-05-14 11:43:20 +1000
committerPaul Mackerras <paulus@samba.org>2007-05-17 21:11:13 +1000
commite3d67b663b5ededac1b2c552b4f0b4fbe94d7ac3 (patch)
tree2875f48c35991ee861594ae664ea72c2705bb32e /include/asm-powerpc/grackle.h
parent39d207036c76ff16650772b83fb1a12ab788ca26 (diff)
downloadkernel-crypto-e3d67b663b5ededac1b2c552b4f0b4fbe94d7ac3.tar.gz
kernel-crypto-e3d67b663b5ededac1b2c552b4f0b4fbe94d7ac3.tar.xz
kernel-crypto-e3d67b663b5ededac1b2c552b4f0b4fbe94d7ac3.zip
[POWERPC] Remove fixup_bigphys_addr() for arch/powerpc to avoid link error
There are no actual implementations of fixup_bigphys_addr() in arch/powerpc, and with a 64-bit aware ioremap() and so forth, it should no longer be necessary. This patch removes the last dregs of fixup_bigphys_addr() from arch/powerpc. In fact, the only reason this hasn't caused link errors already is that nobody must have tried using one of the small number of drivers using io_remap_pfn_range() on one of the small number of platforms which are 32-bit but define CONFIG_PHYS_64BIT. Nonetheless this fixes a bug, and should go into 2.6.22. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'include/asm-powerpc/grackle.h')
0 files changed, 0 insertions, 0 deletions