From: Jassi Brar <jassisinghbrar@gmail.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
linux-samsung-soc@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
Abhilash Kesavan <a.kesavan@samsung.com>,
dbrownell@users.sourceforge.net, ben-linux@fluff.org
Subject: Re: [PATCH] SPI: S5P64X0: Enable SPI driver for S5P6440 and S5P6450
Date: Fri, 3 Dec 2010 19:12:21 +0900 [thread overview]
Message-ID: <AANLkTin1UkkQOhtScPqsPGMPJYPQuVhj9ddXZhbYddkj@mail.gmail.com> (raw)
In-Reply-To: <015201cb92d0$d03777a0$70a666e0$%kim@samsung.com>
On Fri, Dec 3, 2010 at 6:59 PM, Kukjin Kim <kgene.kim@samsung.com> wrote:
> Sangbeom Kim wrote:
>>
>> From: Abhilash Kesavan <a.kesavan@samsung.com>
>>
>> This patch enable the existing S3C64XX series SPI driver for S5P64X0
>>
>> Signed-off-by: Abhilash Kesavan <a.kesavan@samsung.com>
>> Signed-off-by: Sangbeom Kim <sbkim73@samsung.com>
>> ---
>> drivers/spi/Kconfig | 4 ++--
>
> Added following mailing list and maintainers.
> spi-devel-general@lists.sourceforge.net
> David Brownell and Grant Likely (SPI Subsystem's maintainer)
I would have appreciated being CC'ed.
>> config SPI_S3C64XX
>> tristate "Samsung S3C64XX series type SPI"
>> - depends on ARCH_S3C64XX && EXPERIMENTAL
>> - select S3C64XX_DMA
>> + depends on (ARCH_S3C64XX || ARCH_S5P64X0) && EXPERIMENTAL
>
> Do we really still need CONFIG_EXPERIMENTAL here?
I think we can drop it.
>> + select S3C64XX_DMA if !ARCH_S5P64X0
>> help
>> SPI driver for Samsung S3C64XX and newer SoCs.
>
> SPI driver for Samsung S3C64XX, S5P64X0 and newer Socs.
S5P64X0 is already a part of 'newer Socs'
prev parent reply other threads:[~2010-12-03 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291338253-16461-1-git-send-email-sbkim73@samsung.com>
[not found] ` <1291338253-16461-1-git-send-email-sbkim73-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-12-03 9:59 ` [PATCH] SPI: S5P64X0: Enable SPI driver for S5P6440 and S5P6450 Kukjin Kim
2010-12-03 10:12 ` Jassi Brar [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=AANLkTin1UkkQOhtScPqsPGMPJYPQuVhj9ddXZhbYddkj@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=a.kesavan@samsung.com \
--cc=ben-linux@fluff.org \
--cc=dbrownell@users.sourceforge.net \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sbkim73@samsung.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;
as well as URLs for NNTP newsgroup(s).