mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Kevin Wells <kevin.wells@nxp.com>,
	"vitalywool@gmail.com" <vitalywool@gmail.com>,
	"khali@linux-fr.org" <khali@linux-fr.org>,
	"ben-linux@fluff.org" <ben-linux@fluff.org>,
	"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Srinivas Bakki <srinivas.bakki@nxp.com>,
	"aletes.xgr@gmail.com" <aletes.xgr@gmail.com>,
	"jonsmirl@gmail.com" <jonsmirl@gmail.com>
Subject: Re: [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions
Date: Mon, 03 Sep 2012 22:16:22 +0200	[thread overview]
Message-ID: <50451016.7010608@antcom.de> (raw)
In-Reply-To: <20120820175527.GA9169@pengutronix.de>

Hi Wolfram,

On 20/08/12 19:55, Wolfram Sang wrote:
>> I've never had my hands on a PNX4008 chip at NXP, but I do
>> believe they are the same IP. That specific I2C IP was used in a
>> number of NXP/Phillips chips besides the PNX4008/LPC32xx. I don't
>> think there are any PNX4008's in the wild, and even working in
>> NXP, I can't find any non-marketing reference material for that
>> part (including the user manual).
> 
> Thanks for the heads up. I'll apply both patches, then.

Should I consider the two patches as applied now (where?
i2c-embedded?), or should I resend? ;-)

Thanks in advance,

Roland

  parent reply	other threads:[~2012-09-03 20:16 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 ` [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions Wolfram Sang
2012-08-19  8:47   ` 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 [this message]
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=50451016.7010608@antcom.de \
    --to=stigge@antcom.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=vitalywool@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
Powered by JetHome