From: Fabio Estevam <fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: "Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org
Subject: Re: [PATCH v2] i2c: mxs: Let i2c-mxs be built for MX23
Date: Fri, 21 Oct 2011 16:59:52 -0200 [thread overview]
Message-ID: <4EA1C128.106@freescale.com> (raw)
In-Reply-To: <20111021184822.GJ15299-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Hi Uwe,
On 10/21/2011 4:48 PM, Uwe Kleine-König wrote:
> On Fri, Oct 21, 2011 at 04:27:44PM -0200, Fabio Estevam wrote:
>> MX23 and MX28 share the same I2C block, so let i2c-mxs be built for MX23 too.
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> arch/arm/mach-mxs/devices/platform-mxs-i2c.c doesn't support i.MX23 yet,
> but still I think the change is correct.
Yes, I know. I plan to submit the I2C arch/arm/mach-mxs related patches next week.
> Acked-by: Uwe Kleine-König <u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Thanks,
Fabio Estevam
next prev parent reply other threads:[~2011-10-21 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 18:27 [PATCH v2] i2c: mxs: Let i2c-mxs be built for MX23 Fabio Estevam
[not found] ` <1319221664-3018-1-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-10-21 18:48 ` Uwe Kleine-König
[not found] ` <20111021184822.GJ15299-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-10-21 18:59 ` Fabio Estevam [this message]
[not found] ` <4EA1C128.106-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2011-10-22 14:57 ` 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=4EA1C128.106@freescale.com \
--to=fabio.estevam-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.