public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: David Brownell <david-b@pacbell.net>,
	"Syed, Rafiuddin" <rafiuddin.syed@ti.com>,
	"spi-devel-general@lists.sourceforge.net"
	<spi-devel-general@lists.sourceforge.net>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH]OMAP4: McSPI Support for OMAP_4430
Date: Wed, 5 Aug 2009 11:58:15 +0300	[thread overview]
Message-ID: <20090805085815.GC7374@atomide.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02B55019A3@dbde02.ent.ti.com>

* Shilimkar, Santosh <santosh.shilimkar@ti.com> [090703 07:52]:
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org 
> > [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of David Brownell
> > Sent: Friday, July 03, 2009 5:57 AM
> > To: Syed, Rafiuddin
> > Cc: spi-devel-general@lists.sourceforge.net; 
> > linux-omap@vger.kernel.org
> > Subject: Re: [PATCH]OMAP4: McSPI Support for OMAP_4430
> > 
> > On Monday 29 June 2009, Syed Rafiuddin wrote:
> > > 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@ti.com>
> > > Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
> > > Acked-by: Tony Lindgren <tony@atomide.com>
> > > Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> > 
> > I'd add my ack if this patch weren't mangled.  :)
> > 
> > > ---
> > >  arch/arm/mach-omap2/devices.c |   25 +++++++++++++++++++++----
> > 
> > Since *most* of this is arch/arm stuff, I think this patch
> > should go to mainine through Tony.  That's the best way to
> > make sure it doesn't cause conflicts with other patches he
> > sends.
> 
> Tony suggested that this patch can be sent through SPI mailing list.
> Refer this thread.
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg14011.html 

Just to confirm, this is OK for me to merge via the SPI once the
mangling is removed.

Tony



> > 
> > >  drivers/spi/omap2_mcspi.c     |   10 ++++++----
> > >  2 files changed, 27 insertions(+), 8 deletions(-)
> > 
> > None of this seemed particularly controversial.
> > 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-08-05  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-29 12:55 [PATCH]OMAP4: McSPI Support for OMAP_4430 Syed Rafiuddin
2009-06-29 17:58 ` Pandita, Vikram
2009-07-03  0:27 ` David Brownell
2009-07-03  4:51   ` Shilimkar, Santosh
2009-08-05  8:58     ` Tony Lindgren [this message]
2009-08-05  9:10       ` Syed Rafiuddin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090805085815.GC7374@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=rafiuddin.syed@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox