public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] i2c: zynq: Support for 0-length register address
Date: Thu, 30 Jan 2014 06:26:51 +0100	[thread overview]
Message-ID: <52E9E29B.2000703@denx.de> (raw)
In-Reply-To: <91aa2703a9aa115669abd6fce8c7761d2695f476.1390380363.git.michal.simek@xilinx.com>

Hello Michal,

Am 22.01.2014 09:46, schrieb Michal Simek:
> From: Michael Burr<michael.burr@logicpd.com>
>
> Fixed bug with alen == 0 in 'i2c_write', 'i2c_read'
> Further minor corrections:
> - Write 'address' register before 'data' register.
> - Write 'transfer_size' register before 'address' register.
>
> Signed-off-by: Michael Burr<michael.burr@logicpd.com>
> Signed-off-by: Michal Simek<michal.simek@xilinx.com>
>
> ---
>
> Changes in v2:
> - Fix incorrect rebase
>
> Changes in v1:
> - Based on original thread from Michael Burr
>    http://lists.denx.de/pipermail/u-boot/2013-October/165060.html
> - MS rebase on latest&greatest
>
>   drivers/i2c/zynq_i2c.c | 42 +++++++++++++++++++++++-------------------
>   1 file changed, 23 insertions(+), 19 deletions(-)

Applied to u-boot-i2c.git, thanks!

bye,
Heiko
-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  parent reply	other threads:[~2014-01-30  5:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22  8:46 [U-Boot] [PATCH v2 1/2] i2c: zynq: Support for 0-length register address Michal Simek
2014-01-22  8:46 ` [U-Boot] [PATCH v2 2/2] i2c: zynq: Add support for the second i2c controller Michal Simek
2014-01-30  5:27   ` Heiko Schocher
2014-01-30  5:26 ` Heiko Schocher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-10-15 17:18 [U-Boot] [PATCH v2 0/2] I2C: Zynq Michael Burr
2013-10-15 17:18 ` [U-Boot] [PATCH v2 1/2] I2C: Zynq: Support for 0-length register address Michael Burr

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=52E9E29B.2000703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox