[PATCH 2.6-BK] [ARM] Trivial ARM fixes for 2.6.8

From: Deepak Saxena
Date: Thu Jul 29 2004 - 14:21:46 EST


Andrew, Linus

Russell King is out vacationing for the next 2 weeks so I can't
push any ARM updates through him and I have have some trivial
fixes that I'd like to get upstream into 2.6.8. If you're OK
with pulling them directly from me, please do a

bk pull bk://dsaxena.bkbits.net/linux-2.6-for-rmk

This will update the following files:

arch/arm/mach-ixp4xx/common-pci.c | 2 ++
arch/arm/mach-ixp4xx/coyote-setup.c | 8 ++++++--
arch/arm/mach-ixp4xx/ixdp425-setup.c | 10 +++++++---
arch/arm/mach-ixp4xx/prpmc1100-setup.c | 8 ++++++--
include/asm-arm/bitops.h | 2 +-
5 files changed, 22 insertions(+), 8 deletions(-)

through these ChangeSets:

<dsaxena@xxxxxxxxxxx> (04/07/16 1.1784.14.4)
[ARM] Fix _find_next_bit_be prototype to use 'const' qualifier

_find_next_bit_be() does not have a 'const' qualifier for the first
argument, so we get the following warning for a very large number
of files:

In file included from include/linux/sched.h:15,
from include/linux/module.h:10,
from drivers/mtd/maps/ixp2000.c:24:
include/linux/cpumask.h: In function `__next_cpu':
include/linux/cpumask.h:216: warning: passing arg 1 of `_find_next_bit_be'
discards qualifiers from pointer target type

Signed-off-by: Deepak Saxena <dsaxena@xxxxxxxxxxx>

<dsaxena@xxxxxxxxxxx> (04/07/15 1.1784.14.3)
[ARM] Export ixp42xx_pci_read/write so PCI driver modules load

Originally found by Thomas Winkler <winkler@xxxxxxxxxxxxxxxxx>

Signed-off-by: Deepak Saxena <dsaxena@xxxxxxxxxxx>

<dsaxena@xxxxxxxxxxx> (04/07/07 1.1784.14.1)
[ARM] IXP4xx: platform_add_device() to platform_add_devices() conversion

Signed-off-by: Deepak Saxena <dsaxena@xxxxxxxxxxx>

Tnx!
~Deepak

--
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/

"Unlike me, many of you have accepted the situation of your imprisonment and
will die here like rotten cabbages." - Number 6
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/