public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Syed Rafiuddin <rafiuddin.syed@ti.com>
Cc: spi-devel-general@lists.sourceforge.net, linux-omap@vger.kernel.org
Subject: Re: [PATCH]OMAP4: McSPI Support for OMAP_4430
Date: Thu, 2 Jul 2009 17:27:11 -0700	[thread overview]
Message-ID: <200907021727.12048.david-b@pacbell.net> (raw)
In-Reply-To: <38905.192.168.10.89.1246280107.squirrel@dbdmail.itg.ti.com>

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.


>  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

  parent reply	other threads:[~2009-07-03  0:50 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 [this message]
2009-07-03  4:51   ` Shilimkar, Santosh
2009-08-05  8:58     ` Tony Lindgren
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=200907021727.12048.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=rafiuddin.syed@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