From: Wolfram Sang <w.sang@pengutronix.de>
To: Roland Stigge <stigge@antcom.de>, kevin.wells@nxp.com
Cc: vitalywool@gmail.com, khali@linux-fr.org, ben-linux@fluff.org,
grant.likely@secretlab.ca, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, kevin.wells@nxp.com,
srinivas.bakki@nxp.com, aletes.xgr@gmail.com, jonsmirl@gmail.com
Subject: Re: [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions
Date: Sat, 18 Aug 2012 11:51:08 +0200 [thread overview]
Message-ID: <20120818095108.GB24812@pengutronix.de> (raw)
In-Reply-To: <1344411752-23469-1-git-send-email-stigge@antcom.de>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Wed, Aug 08, 2012 at 09:42:31AM +0200, Roland Stigge wrote:
> The I2C Control Register bits RFDAIE and RFFIE were mixed up. In addition to
> this fix, this patch adds the missing bit DRSIE for completeness.
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
> ---
> Applies to v3.6-rc1
>
> This patch for i2c-pnx affects PNX4008 and LPC32xx (and LPC31xx, not yet in
> mainline). Can you please test and double-check the manuals of PNX4008 and
> LPC31xx? I only found this via the manual of LPC32xx but assume it's the same
> for the others, also.
>
> Thanks in advance!
Kevin, since the other manuals seem to be not easily available, can you
please check?
Thanks,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-08-18 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 7:42 Roland Stigge
2012-08-08 7:42 ` [PATCH RESEND 2/2] i2c: pnx: Fix read transactions of >= 2 bytes Roland Stigge
2012-08-18 9:52 ` Wolfram Sang
2012-08-19 8:45 ` Roland Stigge
2012-08-18 9:51 ` Wolfram Sang [this message]
2012-08-19 8:47 ` [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions Roland Stigge
2012-08-20 16:26 ` Kevin Wells
2012-08-20 16:47 ` Roland Stigge
2012-08-20 19:49 ` Arnd Bergmann
2012-08-20 17:55 ` Wolfram Sang
2012-08-20 20:47 ` Roland Stigge
2012-09-03 20:16 ` Roland Stigge
2012-09-04 9:20 ` 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=20120818095108.GB24812@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=aletes.xgr@gmail.com \
--cc=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=jonsmirl@gmail.com \
--cc=kevin.wells@nxp.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.de \
--cc=vitalywool@gmail.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
Powered by JetHome