From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/5] I2C cleanup before removal of deprecated commands
Date: Mon, 27 Apr 2009 09:22:33 +0200 [thread overview]
Message-ID: <49F55D39.1030606@denx.de> (raw)
In-Reply-To: <cover.1240604094.git.ptyser@xes-inc.com>
Hello Peter,
Peter Tyser wrote:
> Hi Heiko,
> These 5 patches should clean up the compile issues that you noticed
> after application of the "[PATCH v2 0/7] Remove individual I2C commands
> and cleanup" series.
Thanks.
> I only have a build environment for powerpc boards so it'd be much
> appreciated if other architectures could do some basic compile
> testing after the "Remove individual I2C commands and cleanup"
> series is applied to the i2c repository.
I did a "powerpc" and an "arm" MAKEALL ... Hmm.. maybe we should
add somewhere in the tree a documentation, where toolchains can be found?
> Assuming these patches are accepted, the original "v2 Remove individual
> I2C commands and cleanup" series should then be applied.
Applied to u-boot-i2c next branch, also the "v2 Remove individual I2C
commands and cleanup" series, see:
http://git.denx.de/?p=u-boot/u-boot-i2c.git;a=shortlog;h=refs/heads/next
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2009-04-27 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 20:34 [U-Boot] [PATCH 0/5] I2C cleanup before removal of deprecated commands Peter Tyser
2009-04-24 20:34 ` [U-Boot] [PATCH 1/5] i2c.h: Provide a default CONFIG_SYS_I2C_SLAVE value Peter Tyser
2009-04-24 20:34 ` [U-Boot] [PATCH 2/5] cpci750: i2c cleanup Peter Tyser
2009-04-24 20:34 ` [U-Boot] [PATCH 3/5] Marvell: " Peter Tyser
2009-04-24 20:34 ` [U-Boot] [PATCH 4/5] mpc7448hpc2: Add CONFIG_SYS_I2C_SPEED define Peter Tyser
2009-04-24 20:34 ` [U-Boot] [PATCH 5/5] tsi108_i2c: Add i2c_init() stub function Peter Tyser
2009-04-27 7:22 ` 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=49F55D39.1030606@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