* Shilimkar, Santosh <santosh.shilimkar@xxxxxx> [090626 08:00]: > > -----Original Message----- > > From: linux-omap-owner@xxxxxxxxxxxxxxx > > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin Hilman > > Sent: Thursday, June 25, 2009 10:15 PM > > To: Syed, Rafiuddin > > Cc: linux-omap@xxxxxxxxxxxxxxx > > Subject: Re: [RESUBMIT][PATCH][RFC] OMAP4: McSPI Support for OMAP_4430 > > > > "Syed Rafiuddin" <rafiuddin.syed@xxxxxx> writes: > > > > > This patch adds McSPI support for OMAP4430 SDP platform. > > All the base addresses > > > are changed between OMAP1/2/3 and OMAP4.The fields of the > > resource structures > > > are filled at runtime to have McSPI support on OMAP4. > > > > > > Signed-off-by: Syed Rafiuddin <rafiuddin.syed@xxxxxx> > > > > This driver needs some help for multi-omap, but that problem existed > > before this patch, so > > > > Acked-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > > > > > > > --- > > > arch/arm/mach-omap2/devices.c | 25 +++++++++++++++++++++---- > > > drivers/spi/omap2_mcspi.c | 10 ++++++---- > > > 2 files changed, 27 insertions(+), 8 deletions(-) > Not sure but looks like the patch needs split since different upstream paths > 1. arch/arm/mach-omap2/devices.c -- linux-arm > 2. drivers/spi/omap2_mcspi.c --- Don't know the list but should be some driver list. > > Is that correct ? I think this is OK to send as a single patch via the SPI list. Acked-by: Tony Lindgren <tony@xxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
