summaryrefslogtreecommitdiff
path: root/drivers/staging/zcache
diff options
context:
space:
mode:
authorOmar Ramirez Luna <omar.ramirez@ti.com>2012-04-20 20:22:41 -0500
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-24 11:57:36 -0700
commita2cd62ec9a3a2805014bdc14e0644b5faa352d3c (patch)
treeb4583526aae2f5e6ad809b08f0a07918157a9ce6 /drivers/staging/zcache
parent66f75a5d028beaf67c931435fdc3e7823125730c (diff)
downloadlinux-3.10-a2cd62ec9a3a2805014bdc14e0644b5faa352d3c.tar.gz
linux-3.10-a2cd62ec9a3a2805014bdc14e0644b5faa352d3c.tar.bz2
linux-3.10-a2cd62ec9a3a2805014bdc14e0644b5faa352d3c.zip
staging: tidspbridge: remove usage of OMAP2_L4_IO_ADDRESS
Instead now use ioremap. This is needed for 3.4 since this change emerged in mainline during one of the previous rc cycles. These solves the following compilation breaks: drivers/staging/tidspbridge/core/tiomap3430.c: In function ‘bridge_brd_start’: drivers/staging/tidspbridge/core/tiomap3430.c:425:4: error: implicit declaration of function ‘OMAP2_L4_IO_ADDRESS’ drivers/staging/tidspbridge/core/wdt.c: In function ‘dsp_wdt_init’: drivers/staging/tidspbridge/core/wdt.c:56:2: error: implicit declaration of function ‘OMAP2_L4_IO_ADDRESS’ For control registers a new function needs to be defined so we can get rid of a layer violation, but that approach must be queued for the next merge window. As seen in: http://www.arm.linux.org.uk/developer/build/ platform: omap4430-sdp build: uImage config: randconfig version: 3.4.0-rc3 start time: Apr 20 2012 01:07 Reported-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/zcache')
0 files changed, 0 insertions, 0 deletions