From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [i2c] v2 Pull request
Date: Mon, 20 Jan 2014 10:45:58 +0100 [thread overview]
Message-ID: <52DCF056.30509@denx.de> (raw)
In-Reply-To: <52DA2D1D.5070504@denx.de>
Hello Tom
Updated pull request for u-boot-i2c, as the zynq patches had problems,
see:
http://lists.denx.de/pipermail/u-boot/2014-January/171352.html
So, here the correct pull-request:
The following changes since commit 7f673c99c2d8d1aa21996c5b914f06d784b080ca:
Merge branch 'master' of git://git.denx.de/u-boot-arm (2014-01-10 10:56:00 -0500)
are available in the git repository at:
git://git.denx.de/u-boot-i2c.git master
for you to fetch changes up to dccacbe01968f9e682cb1dc9b7d43c831897cbec:
i2c: fti2c010: fix compiler warning on paddr[] (2014-01-13 08:18:38 +0100)
----------------------------------------------------------------
Alexey Brodkin (2):
env_eeprom - fix bus recovery for "eeprom_bus_read"
drivers/designware_i2c - add suppor of CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW
Darwin Rambo (1):
i2c: Fix i2c speed command
Hisashi Nakamura (1):
rcar_i2c: Fix receiving wait condition
Kuo-Jung Su (1):
i2c: fti2c010: fix compiler warning on paddr[]
Nobuhiro Iwamatsu (1):
rcar_i2c: Clear status before start master receive
common/env_eeprom.c | 5 ++---
drivers/i2c/designware_i2c.c | 38 ++++++++++++++++++++++++++++++++++++++
drivers/i2c/fti2c010.c | 4 ++--
drivers/i2c/i2c_core.c | 2 +-
drivers/i2c/rcar_i2c.c | 6 ++++--
5 files changed, 47 insertions(+), 8 deletions(-)
Thanks!
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:[~2014-01-20 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 7:28 [U-Boot] [i2c] Pull request Heiko Schocher
2014-01-20 9:24 ` Michal Simek
2014-01-20 9:34 ` Alexey Brodkin
2014-01-20 9:41 ` Michal Simek
2014-01-20 9:45 ` Heiko Schocher [this message]
2014-01-20 22:58 ` [U-Boot] [i2c] v2 " 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=52DCF056.30509@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.