[PATCH 0/6] staging: tidspbridge fixes for 3.7
Greg Kroah-Hartman
gregkh at linuxfoundation.org
Wed Oct 24 22:28:54 UTC 2012
On Wed, Oct 24, 2012 at 05:09:14PM -0500, Omar Ramirez Luna wrote:
> 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
Are the "fix up the compiler warning" patches really needed for 3.7?
Are they new in 3.7-rc1? Or were they there before in 3.6?
thanks,
greg k-h
More information about the devel
mailing list