Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

2012-10-24 Thread Greg Kroah-Hartman
On Wed, Oct 24, 2012 at 06:25:42PM -0500, Omar Ramirez Luna wrote: > Hi, > > On Wed, Oct 24, 2012 at 5:28 PM, Greg Kroah-Hartman > wrote: > > 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 reque

Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

2012-10-24 Thread Omar Ramirez Luna
Hi, On Wed, Oct 24, 2012 at 5:28 PM, Greg Kroah-Hartman wrote: > 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

Re: [PATCH 0/6] staging: tidspbridge fixes for 3.7

2012-10-24 Thread Greg Kroah-Hartman
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

[PATCH 0/6] staging: tidspbridge fixes for 3.7

2012-10-24 Thread Omar Ramirez Luna
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 writeba