From: Alexander Kochetkov <al.kochet@gmail.com>
To: Felipe Balbi <balbi@ti.com>, Aaro Koskinen <aaro.koskinen@iki.fi>,
Wolfram Sang <wsa@the-dreams.de>
Cc: linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] i2c: omap: fix i207 errata handling
Date: Sat, 22 Nov 2014 02:02:03 +0300 [thread overview]
Message-ID: <B174E67D-9CCF-48B6-A5E5-911668161823@gmail.com> (raw)
In-Reply-To: <20141121160828.GP7508@saruman>
21 нояб. 2014 г., в 19:08, Felipe Balbi <balbi@ti.com> написал(а):
> Tested on BBB and AM437x Starter Kit
>
> Tested-by: Felipe Balbi <balbi@ti.com>
> Reviewed-by: Felipe Balbi <balbi@ti.com>
21 нояб. 2014 г., в 0:10, Aaro Koskinen <aaro.koskinen@iki.fi> написал(а):
> I could not see any breakage or anything wrong on OMAP2 & OMAP3.
> On OMAP1 I don't have anything on the OMAP I2C bus, so cannot really
> test anything there.
>
> Tested-by: Aaro Koskinen <aaro.koskinen@iki.fi>
21 нояб. 2014 г., в 21:11, Wolfram Sang <wsa@the-dreams.de> написал(а):
> The errno for AL is -EAGAIN. Curly braces are not needed.
Guys, I really appreciate you help.
So much testing and review.
I could not have done one.
Thank you!
Alexander.
next prev parent reply other threads:[~2014-11-21 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 0:16 [PATCH] i2c: omap: fix i207 errata handling Alexander Kochetkov
2014-11-21 0:29 ` Alexander Kochetkov
[not found] ` <089B5BDA-682D-46B6-869F-A6ADDFE691C3-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-21 23:16 ` Alexander Kochetkov
2014-11-21 16:08 ` Felipe Balbi
2014-11-21 23:02 ` Alexander Kochetkov [this message]
[not found] ` <B174E67D-9CCF-48B6-A5E5-911668161823-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-22 21:13 ` Wolfram Sang
2014-11-22 21:08 ` 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=B174E67D-9CCF-48B6-A5E5-911668161823@gmail.com \
--to=al.kochet@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).