All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 16/17] mpc83xx: Replace fdt_node_offset() with fdt_find_node_by_path().
Date: Wed, 11 Jul 2007 21:12:31 -0400	[thread overview]
Message-ID: <46957FFF.4040508@gmail.com> (raw)
In-Reply-To: <20070711194645.e8535a6b.kim.phillips@freescale.com>

Kim Phillips wrote:

[snip]

> Hi gvb,
> 
> there were a couple of minor issues I fixed up in patches 16 & 17:
> 
> o stale CONFIG_MPC83XX_TSECx cruft
> 
> o unnecessary OF_TBCLK ifdefs (all applicable boards define it, and
> linux' calibration loop doesn't exit without it)
> 
> o mutual exclusion with CONFIG_OF_FLAT_TREE
> 
> o minor whitespace inconsistencies
> 
> I decided to save time and fix them in place.  I applied them to the
> mpc83xx branch on u-boot-mpc83xx.git.

Excellent!

> The master branch of u-boot-mpc83xx.git still reflects WD's master.
> Since the mpc83xx branch doesn't compile for the 8360, and since
> everyone should be on u-boot-testing anyway, I merged u-boot-testing,
> u-boot-fdt (minus 16 & 17), and the mpc83xx branch into the testing
> branch of u-boot-mpc83xx.git.
> 
> Functionality is looking good, esp. thanks to your fixups, gvb, thanks.
> 
> So, 83xx users, please test u-boot-mpc83xx.git#testing.
> 
> Thanks,
> 
> Kim

Even better!  I was just debating how adventurous I would be tonight, 
whether I should try applying Jon's patchzilla on u-boot-fdt.  You just 
did it for me.  Even better.  ;-)

Thanks again,
gvb

      reply	other threads:[~2007-07-12  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  1:27 [U-Boot-Users] [PATCH 16/17] mpc83xx: Replace fdt_node_offset() with fdt_find_node_by_path() Jerry Van Baren
2007-07-05  3:06 ` Grant Likely
2007-07-12  0:46 ` Kim Phillips
2007-07-12  1:12   ` Jerry Van Baren [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=46957FFF.4040508@gmail.com \
    --to=gvb.uboot@gmail.com \
    --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.