From: Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: 'Kyungmin Park' <kmpark-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
'Naveen Krishna Ch'
<ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
Subject: RE: [PATCH 3/3] i2c/busses: Select I2C bus support for S5PV210 and S5P6440.
Date: Mon, 19 Jul 2010 09:24:54 +0900 [thread overview]
Message-ID: <000101cb26d8$d2c74fe0$7855efa0$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTikqjZVKDgCIuZ0QCvzrzdrNmGUOq2YZyqb0TKZn-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Kyungmin Park wrote:
>
> On Fri, Jul 16, 2010 at 10:13 PM, Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
wrote:
> > From: Naveen Krishna Ch <ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> >
> > This patch is to select support I2C channels 0, 1 and 2 for S5PV210 and
> S5P6440.
> >
> > Signed-off-by: Naveen Krishna Ch <ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> > Signed-off-by: Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
> > ---
> > drivers/i2c/busses/Kconfig | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> > index bceafbf..e553fe8 100644
> > --- a/drivers/i2c/busses/Kconfig
> > +++ b/drivers/i2c/busses/Kconfig
> > @@ -523,7 +523,7 @@ config I2C_PXA_SLAVE
> >
> > config I2C_S3C2410
> > tristate "S3C2410 I2C Driver"
> > - depends on ARCH_S3C2410 || ARCH_S3C64XX
> > + depends on ARCH_S3C2410 || ARCH_S3C64XX || ARCH_S5PV210 ||
> ARCH_S5P6440
>
> Are there any SoCs don't have i2c? If no, how about to just depends on
> PLAT_SAMSUNG.
>
Looks good..will change it.
Thanks for your suggestion.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2010-07-19 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 13:13 [PATCH 0/3] Add support I2C devices on SMDK6440, SMDKC110 and SMDKV210 Kukjin Kim
[not found] ` <1279285999-27555-1-git-send-email-kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2010-07-16 13:13 ` [PATCH 1/3] ARM: S5P6440: Add support for I2C channel 0 and 1 on SMDK6440 Kukjin Kim
2010-07-16 13:13 ` [PATCH 2/3] ARM: S5PV210: Add support for I2C devices on SMDKV210 and SMDKC110 Kukjin Kim
2010-07-16 13:43 ` Kyungmin Park
2010-07-19 0:29 ` Kukjin Kim
2010-07-16 13:13 ` [PATCH 3/3] i2c/busses: Select I2C bus support for S5PV210 and S5P6440 Kukjin Kim
2010-07-16 13:41 ` Kyungmin Park
[not found] ` <AANLkTikqjZVKDgCIuZ0QCvzrzdrNmGUOq2YZyqb0TKZn-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-19 0:24 ` Kukjin Kim [this message]
2010-07-21 10:50 ` Kukjin Kim
2010-07-16 13:39 ` [PATCH 0/3] Add support I2C devices on SMDK6440, SMDKC110 and SMDKV210 Kyungmin Park
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='000101cb26d8$d2c74fe0$7855efa0$%kim@samsung.com' \
--to=kgene.kim-sze3o3uu22jbdgjk7y7tuq@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org \
--cc=kmpark-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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).