From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Tomasz Figa' <tomasz.figa@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
'Wolfram Sang' <w.sang@pengutronix.de>,
'Giridhar Maruthy' <giridhar.m@samsung.com>
Subject: RE: [PATCH] i2c: s3c2410: Add quirk to exclude GPIO config for exynos5440
Date: Sun, 20 Jan 2013 15:28:24 -0800 [thread overview]
Message-ID: <030f01cdf765$d98a00b0$8c9e0210$@samsung.com> (raw)
In-Reply-To: <1786045.3qNF5pjnvJ@flatron>
Tomasz Figa wrote:
>
> Hi Kukjin,
>
Hi,
> You should also add the new compatible value to the documentation of
> device tree bindings for i2c-s3c2410.
>
Yeah, agreed.
> (Documentation/devicetree/bindings/i2c/i2c-s3c2410.txt)
>
Giridhar, please address comments from Tomasz.
Thanks.
- Kukjin
prev parent reply other threads:[~2013-01-20 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 5:12 [PATCH] i2c: s3c2410: Add quirk to exclude GPIO config for exynos5440 Kukjin Kim
2013-01-19 10:52 ` Tomasz Figa
2013-01-20 23:28 ` Kukjin Kim [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='030f01cdf765$d98a00b0$8c9e0210$@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=giridhar.m@samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tomasz.figa@gmail.com \
--cc=w.sang@pengutronix.de \
/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).