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 03/12] 83xx, kmeter1: add I2C, dtt, eeprom support
Date: Thu, 19 Feb 2009 09:10:51 +0100	[thread overview]
Message-ID: <499D140B.6070001@denx.de> (raw)
In-Reply-To: <20090218185507.4e3663ee.kim.phillips@freescale.com>

Hello Kim,

Kim Phillips wrote:
> On Wed, 18 Feb 2009 09:14:05 +0100
> Heiko Schocher <hs@denx.de> wrote:
[...]
>> But I was wondering why the DTTs are initialized so early. Is this
>> necessary? If not, I don;t need this ...
> 
> I searched and didn't find out why.  If there's no reason then maybe we
> don't need it indeed.

I think so too.

> Meanwhile, I've applied the 'v2' versions of your patches and still
> have trouble building the kmeter1 board*, probably due to inter-patch
> dependencies in this patchseries.  This means at minimum you're breaking
> git-bisection abilities for your boards.  Can you resubmit without
> breaking bisection?

:-( Sorry for that. I am actually learning that I have to look
for such a point too. I always compiled with all off my patches...

This happend, so I think, because the kmeter shares a lot of common
options with other boards from this manufacturer ... and I did a
rework from that common options in patch 10/12 ...

I try to make a new series, without breaking bisection ...

> Also, did you want any of these to go through the mpc83xx
> tree, or should WD pick all of them up?  Please make two separate
> patchseries if you're targeting two trees.

OK, 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-02-19  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 18:25 [U-Boot] [PATCH 03/12] 83xx, kmeter1: add I2C, dtt, eeprom support Heiko Schocher
2009-02-17  1:36 ` Kim Phillips
2009-02-17  6:03   ` Heiko Schocher
2009-02-18  1:22     ` Kim Phillips
2009-02-18  8:14       ` Heiko Schocher
2009-02-19  0:55         ` Kim Phillips
2009-02-19  8:10           ` 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=499D140B.6070001@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