All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v9 0/31] Create generic board init for ARM, x86, PPC
Date: Wed, 13 Mar 2013 14:16:23 +0100	[thread overview]
Message-ID: <51407C27.2030809@gmail.com> (raw)
In-Reply-To: <CAPnjgZ3XmZmm-puyvO0HTXaqnwDden30xMa6xig3QG3s4Ooc_Q@mail.gmail.com>

Hi Simon,

On 03/13/2013 04:52 AM, Simon Glass wrote:
> Hi,
> 
> On Mon, Mar 11, 2013 at 10:03 AM, Simon Glass <sjg@chromium.org> wrote:
>> This series creates a generic board init implementation which contains
>> the essential functions of the major arch/xxx/lib/board.c files. It is
>> split into two parts: board_f.c for pre-relocation and board_r.c for
>> post-relocation.

I tested the whole series on avr32. The minor changes there do not break
runtime behaviour, therefore

Tested-by: Andreas Bie?mann <andreas.biessmann@googlemail.com>

Will this series be applied for upcomming release? I'm asking cause of

http://patchwork.ozlabs.org/patch/225225/

vs

http://patchwork.ozlabs.org/patch/220413/

Best regards

Andreas Bie?mann

  reply	other threads:[~2013-03-13 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1363021453-6566-1-git-send-email-sjg@chromium.org>
2013-03-11 17:50 ` [U-Boot] [PATCH v9 0/31] Create generic board init for ARM, x86, PPC Simon Glass
2013-03-13  3:52 ` Simon Glass
2013-03-13 13:16   ` Andreas Bießmann [this message]
2013-03-13 16:25     ` Tom Rini
2013-03-13 22:20       ` Simon Glass
2013-03-14 17:42         ` Simon Glass
     [not found] <1363020460-14307-1-git-send-email-sjg@chromium.org>
2013-03-11 16:49 ` [U-Boot] [PATCH v9 09/31] Introduce generic pre-relocation board_f.c Simon Glass
2013-03-13  8:46   ` [U-Boot] [PATCH v9 0/31] Create generic board init for ARM, x86, PPC Wolfgang Denk
2013-03-15 22:23     ` Tom Rini
2013-03-30 21:34     ` Simon Glass

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=51407C27.2030809@gmail.com \
    --to=andreas.devel@googlemail.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.