From: Tony Lindgren <tony@atomide.com>
To: "Arce, Abraham" <x0066660@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>
Subject: Re: [PATCH v2 1/3] OMAP4: SPI: Fix Driver Kconfig
Date: Wed, 5 May 2010 10:21:13 -0700 [thread overview]
Message-ID: <20100505172113.GY29604@atomide.com> (raw)
In-Reply-To: <27F9C60D11D683428E133F85D2BB4A53043DEEB8C0@dlee03.ent.ti.com>
* Arce, Abraham <x0066660@ti.com> [100505 00:05]:
> From: Syed Rafiuddin <rafiuddin.syed@ti.com>
>
> Add OMAP4 data to allow McSPI driver built
>
> Signed-off-by: Syed Rafiuddin <rafiuddin.syed@ti.com>
> Signed-off-by: Shubhro <a0393217@ti.com>
> Signed-off-by: Santosh Shilimkar <santosh shilimkar@ti.com>
> Signed-off-by: Abraham Arce <x0066660@ti.com>
> ---
> drivers/spi/Kconfig | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> index a191fa2..f950b63 100644
> --- a/drivers/spi/Kconfig
> +++ b/drivers/spi/Kconfig
> @@ -180,10 +180,10 @@ config SPI_OMAP_UWIRE
> This hooks up to the MicroWire controller on OMAP1 chips.
>
> config SPI_OMAP24XX
> - tristate "McSPI driver for OMAP24xx/OMAP34xx"
> - depends on ARCH_OMAP2 || ARCH_OMAP3
> + tristate "McSPI driver for OMAP"
> + depends on ARCH_OMAP2PLUS
> help
> - SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
> + SPI master controller for OMAP24XX and later Multichannel SPI
> (McSPI) modules.
>
> config SPI_OMAP_100K
Planning on merging this via omap tree so we get the omap4 Ethernet
working. That is after the related patch has been updated to check
the result from gpio_request.
Anybody from the spi list care to ack this?
Regards,
Tony
prev parent reply other threads:[~2010-05-05 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 7:09 [PATCH v2 1/3] OMAP4: SPI: Fix Driver Kconfig Arce, Abraham
2010-05-05 17:21 ` Tony Lindgren [this message]
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=20100505172113.GY29604@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=x0066660@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).