From: Wolfram Sang <wsa@the-dreams.de>
To: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
Cc: linux-i2c@vger.kernel.org, naveenkrishna.ch@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, sjg@chromium.org,
grundler@chromium.org, linux-kernel@vger.kernel.org,
cpgs@samsung.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] i2c: exynos: add support for HSI2C module on Exynos7
Date: Fri, 3 Oct 2014 03:34:05 +0200 [thread overview]
Message-ID: <20141003013404.GI1323@katana> (raw)
In-Reply-To: <1410859998-29285-2-git-send-email-ch.naveen@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
On Tue, Sep 16, 2014 at 03:03:17PM +0530, Naveen Krishna Chatradhi wrote:
> The HSI2C module on Exynos7 differs in the transfer status
> bits. Transfer status bits were moved to INT_ENABLE and
> INT_STATUS registers
>
> This patch adds support for the HSI2C module on Exynos7.
> 1. Implementes a "hw" field in the variant struct to distinguish
> the hardware.
> 2. Updates the dt-new compatible in dt-binding documenation
>
> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
Applied to for-next, thanks!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-03 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 9:33 [PATCH 0/2] i2c: Add i2c support for Exynos7 SoC Naveen Krishna Chatradhi
2014-09-16 9:33 ` [PATCH 1/2] i2c: exynos: add support for HSI2C module on Exynos7 Naveen Krishna Chatradhi
2014-10-03 1:34 ` Wolfram Sang [this message]
2014-09-16 9:33 ` [PATCH 2/2] i2c: exynos5: Add Kconfig dependencies Naveen Krishna Chatradhi
2014-10-03 1:34 ` Wolfram Sang
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=20141003013404.GI1323@katana \
--to=wsa@the-dreams.de \
--cc=ch.naveen@samsung.com \
--cc=cpgs@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=grundler@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=naveenkrishna.ch@gmail.com \
--cc=sjg@chromium.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).