From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Steven King <sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
uClinux development list
<uclinux-dev-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org>,
gerg-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [PATCH V3] m68knommu: driver for Freescale Coldfire I2C controller.
Date: Mon, 11 Jun 2012 19:46:34 +0200 [thread overview]
Message-ID: <20120611174634.GI3887@pengutronix.de> (raw)
In-Reply-To: <201205161910.36693.sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Wed, May 16, 2012 at 07:10:35PM -0700, Steven King wrote:
> D'oh! I really dropped the ball on this, but I figure better late than never ;-).
Thank you for this! Yet, I just noticed that the register layout is the
same as in i2c-imx.c. Not surprisingly, since both platforms share the
roots. Have you checked if you can use the imx-driver as well?
Regards,
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-06-11 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 2:10 [PATCH V3] m68knommu: driver for Freescale Coldfire I2C controller Steven King
[not found] ` <201205161910.36693.sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
2012-05-18 6:09 ` Greg Ungerer
2012-06-11 17:46 ` Wolfram Sang [this message]
2012-06-11 19:29 ` Steven King
[not found] ` <201206111229.51887.sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org>
2012-06-12 7:42 ` 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=20120611174634.GI3887@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=gerg-JBU5SbJe1FlAfugRpC6u6w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sfking-xS0NTnu2YfYAvxtiuMwx3w@public.gmane.org \
--cc=uclinux-dev-JBU5SbJe1FlAfugRpC6u6w@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).