From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/3] ARM: I2C: I2C Multi byte address support
Date: Mon, 20 Feb 2012 09:03:25 +0100 [thread overview]
Message-ID: <4F41FE4D.8090906@denx.de> (raw)
In-Reply-To: <CANrkHUas=gFpVd9Ung=QiauzG0oTXL9Xyza1PqBfs972EiryZw@mail.gmail.com>
Hello T Krishnamoorthy
T Krishnamoorthy, Balaji wrote:
> On Mon, Jan 23, 2012 at 3:14 PM, Patil, Rachna <rachna@ti.com> wrote:
>> commit 2faa76196af4b3e93bcb9e38ed9090cbd3b06db3
>> Author: Patil, Rachna <rachna@ti.com>
>> Date: Sun Jan 22 23:44:12 2012 +0000
>>
>> ARM: I2C: I2C Multi byte address support
>>
>> Existing OMAP I2C driver does not support address
>> length greater than one. Hence this patch is to
>> add support for 2 byte address read/write.
>>
>> Signed-off-by: Philip, Avinash <avinashphilip@ti.com>
>> Signed-off-by: Hebbar, Gururaja <gururaja.hebbar@ti.com>
>> Signed-off-by: Patil, Rachna <rachna@ti.com>
[...]
> wrong comment and typo
> This patch series is not really tested for other platform
> like (CONFIG_OMAP243X) || defined(CONFIG_OMAP34XX)
> and the patch is buggy for OMAP4430 panda
:-(
Annoyingly this comment comes too late, as this patch series is in
mainline ... Can you (or Patil) fix this?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2012-02-20 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 9:44 [U-Boot] [PATCH v3 1/3] ARM: I2C: I2C Multi byte address support Patil, Rachna
2012-01-25 6:25 ` Heiko Schocher
2012-02-16 19:33 ` Thomas Weber
2012-02-17 7:05 ` T
2012-02-20 8:03 ` Heiko Schocher [this message]
2012-02-17 9:02 ` Thomas Weber
2012-02-17 9:37 ` Patil, Rachna
2012-02-17 10:08 ` Thomas Weber
2012-02-19 9:44 ` Thomas Weber
2012-02-20 22:23 ` Tom Rini
2012-02-21 8:51 ` Thomas Weber
2012-02-21 14:22 ` Tom Rini
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=4F41FE4D.8090906@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.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 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.