public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 0/2] fdt: Deal correctly with alias nodes
Date: Mon, 27 Feb 2012 17:38:20 +0100	[thread overview]
Message-ID: <201202271738.20471.marex@denx.de> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37966FE474@HQMAIL04.nvidia.com>

> Marek/Simon,
> 
> > -----Original Message-----
> > From: sjg at google.com [mailto:sjg at google.com] On Behalf Of Simon Glass
> > Sent: Sunday, February 26, 2012 7:55 PM
> > To: Marek Vasut; Tom Warren
> > Subject: Re: [U-Boot] [RFC PATCH 0/2] fdt: Deal correctly with alias
> > nodes
> > 
> > +Tom, tegra maintainer
> > 
> > Hi Marek,
> > 
> > On Sun, Feb 26, 2012 at 3:09 PM, Marek Vasut <marex@denx.de> wrote:
> > >> This series proposes a new way to deal with alias nodes and
> > >> introduces a function to take care of it.
> > >> 
> > >> It includes an example of converting USB code over to use this new
> > >> function.
> > >> 
> > >> Note: At present it does not deal automatically with disabled nodes,
> > >> but perhaps it should? Or perhaps this is better as an option.
> > >> Something to leave for later perhaps.
> > >> 
> > >> Note 2: The actual logic of this function is not properly tested yet.
> > >> 
> > >> 
> > >> Simon Glass (2):
> > >>   fdt: Add fdtdec_find_aliases() to deal with alias nodes
> > >>   tegra: Use fdtdec_find_aliases() to find USB ports
> > >> 
> > >>  arch/arm/cpu/armv7/tegra2/usb.c |   17 ++++----
> > >>  include/fdtdec.h                |   51 ++++++++++++++++++++++
> > >>  lib/fdtdec.c                    |   89
> > >> +++++++++++++++++++++++++++++++++++++++ 3 files changed, 148
> > >> insertions(+), 9 deletions(-)
> > > 
> > > Hi,
> > > 
> > > what's the status of this patch/patchset?
> > 
> > I believe it is sitting in the tegra tree ready for a pull request, but
> > waiting on USB. Tom will know.
> 
> Simon is correct. The 18 fdt/USB patches (v5 and 2 from v6) are sitting in
> u-boot-tegra/test waiting on a final ACK for one clock binding DT change
> from Simon based on Stephen's review. As Simon says in answer to a
> separate email, he's working on getting all these to jibe so that I can
> apply them cleanly to u-boot-tegra. As soon as they're ready, I'll apply &
> test and if all goes well, submit a pull request. Then we can move on the
> I2C, LCD, kbd, etc. for Tegra2.
> 
That's good then, I won't care for these and let them go through the tegra tree. 
Thank you for your good work.

M

      reply	other threads:[~2012-02-27 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-26 22:31 [U-Boot] [RFC PATCH 0/2] fdt: Deal correctly with alias nodes Simon Glass
2011-12-26 22:31 ` [U-Boot] [RFC PATCH 1/2] fdt: Add fdtdec_find_aliases() to deal " Simon Glass
2012-01-03 22:34   ` Simon Glass
2012-01-10 20:27   ` Stephen Warren
2012-01-10 21:22     ` Simon Glass
2012-01-10 21:41       ` Stephen Warren
2012-01-12  4:38         ` Simon Glass
2011-12-26 22:31 ` [U-Boot] [RFC PATCH 2/2] tegra: Use fdtdec_find_aliases() to find USB ports Simon Glass
2012-02-26 23:09 ` [U-Boot] [RFC PATCH 0/2] fdt: Deal correctly with alias nodes Marek Vasut
     [not found]   ` <CAPnjgZ3_WgwXJiApa5+5Vs=zUNYnbCyqte=55gpthCeZASdwOA@mail.gmail.com>
2012-02-27 16:36     ` Tom Warren
2012-02-27 16:38       ` Marek Vasut [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=201202271738.20471.marex@denx.de \
    --to=marek.vasut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox