With 3.7-rc1 changes: - New irq numbering in OMAP3 broke the driver request for a mmu irq, until this is migrated to the common iommu framework we can only hardcode the new number. - _raw_* accessors changed a type of one of their parameters with patch "195bbca ARM: 7500/1: io: avoid writeback addressing modes for __raw_ accessors", so the build system was filled with warnings from the old parameter usage. Omar Ramirez Luna (6): staging: tidspbridge: request the right irq for mmu staging: tidspbridge: drop const from custom mmu implementation staging: tidspbridge: change type to __iomem for per and core addresses staging: tidspbridge: ioremap dsp sync addr staging: tidspbridge: ioremap physical address of the stack segment in shm staging: tidspbridge: delete unused mmu functions drivers/staging/tidspbridge/core/tiomap3430.c | 37 +++++-- drivers/staging/tidspbridge/hw/hw_mmu.c | 115 ++++---------------- drivers/staging/tidspbridge/hw/hw_mmu.h | 31 +++--- .../tidspbridge/include/dspbridge/cfgdefs.h | 4 +- .../tidspbridge/include/dspbridge/host_os.h | 4 +- drivers/staging/tidspbridge/rmgr/drv.c | 8 +- drivers/staging/tidspbridge/rmgr/node.c | 21 +++- 7 files changed, 83 insertions(+), 137 deletions(-) -- 1.7.9.5 _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel