public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pieter <phenning@vastech.co.za>
To: u-boot@lists.denx.de
Subject: [U-Boot] Status open patches: 8xxx
Date: Mon, 23 Feb 2009 10:47:52 +0200	[thread overview]
Message-ID: <49A262B8.8060800@vastech.co.za> (raw)
In-Reply-To: <20090222000014.08971832E43F@gemini.denx.de>

Dear Wolfgang

Wolfgang Denk wrote:
> Dear Kim, Andy & Jon,
>
> I have the following patches still marked as open in my list. Could
> you please have a look... 
>
> 8xxx:
> 11/06 Anton Vorontsov    [U-Boot] [PATCH] mpc83xx: increase BOOTMAPSZ to 16MB
> 12/11 Paul Gortmaker     [U-Boot] [PATCH] tsec: report when there is no vendor specific PHY support.
> 12/30 Poonam_Aggrwal-b1  [U-Boot] [PATCH][u-boot-85xx]The 32bit errata fix for 8572 for DDR2 (fwd)
> 01/15 hamoshame Lamotek  [U-Boot] MPC8572DS Registered DDR2 support.
> 01/22 Pieter             [U-Boot] Custom MPC8548 boot using FDT problem
<Snip>

The problem addressed in " 01/22 Pieter   [U-Boot] Custom MPC8548 boot
using FDT problem "  has been resolved and was a combination on defines
in the board.h file and definition in the device tree source. is there
something I need to do to resolve the "open patch status"

regards Pieter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 2722 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090223/902067a7/attachment.bin 

  parent reply	other threads:[~2009-02-23  8:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22  0:00 [U-Boot] Status open patches: 8xxx Wolfgang Denk
2009-02-22  7:13 ` Heiko Schocher
2009-02-23  8:47 ` Pieter [this message]
2009-02-23 18:14 ` Jon Loeliger
2009-02-23 18:53   ` Becky Bruce
2009-02-23 19:58     ` Becky Bruce
2009-02-23 20:41     ` Jon Loeliger
2009-02-23 21:42 ` Kim Phillips
2009-02-23 21:58   ` Wolfgang Denk
2009-03-10 23:06 ` Andy Fleming

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=49A262B8.8060800@vastech.co.za \
    --to=phenning@vastech.co.za \
    --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