All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull u-boot-i2c.git next
Date: Mon, 02 Nov 2009 08:08:19 +0100	[thread overview]
Message-ID: <4AEE8563.4050108@denx.de> (raw)
In-Reply-To: <20091031151156.ED3EFC88C7@gemini.denx.de>

Hello Wolfgang,

Wolfgang Denk wrote:
> Dear Heiko Schocher,
> 
> In message <4AEAF4EB.3050703@denx.de> you wrote:
>> Hello Wolfgang,
>>
>> The following changes since commit f2b4bc04d6aed6be712d236dab48ac4c4da22cbf:
>>   Wolfgang Denk (1):
>>         Merge branch 'master' of git://git.denx.de/u-boot-cfi-flash
>>
>> are available in the git repository at:
>>
>>   git://git.denx.de/u-boot-i2c.git next
>>
>> Mike Frysinger (2):
>>       Blackfin: TWI/I2C: add timeout to transfer
>>       Blackfin: TWI/I2C: implement bus speed get/set functions
>>
>> Valentin Yakovenkov (1):
>>       new PCA9564 i2c bridge driver
>>
>>  drivers/i2c/Makefile       |    1 +
>>  drivers/i2c/bfin-twi_i2c.c |   74 ++++++++++++++---
>>  drivers/i2c/pca9564_i2c.c  |  189 ++++++++++++++++++++++++++++++++++++++++++++
>>  include/pca9564.h          |   50 ++++++++++++
>>  4 files changed, 300 insertions(+), 14 deletions(-)
>>  create mode 100644 drivers/i2c/pca9564_i2c.c
>>  create mode 100644 include/pca9564.h
> 
> Is it correct to assume that you wanted me to pullk this into the "next"
> branch?  This is at least what I did.  Hope it was OK.  Thanks.

Yep, that is correct. Thanks!

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

      reply	other threads:[~2009-11-02  7:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 14:15 [U-Boot] Please pull u-boot-i2c.git next Heiko Schocher
2009-10-31 15:11 ` Wolfgang Denk
2009-11-02  7:08   ` Heiko Schocher [this message]

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=4AEE8563.4050108@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.