From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: barebox@lists.infradead.org, Lior Amsalem <alior@marvell.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCHv2 00/10] kwbimage improvements, Kirkwood support
Date: Wed, 15 May 2013 22:07:18 +0200 [thread overview]
Message-ID: <5193EAF6.2000605@gmail.com> (raw)
In-Reply-To: <1368603396-27887-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 05/15/13 09:36, Thomas Petazzoni wrote:
> Hello,
>
> This is a resend of yesterday patch set, rebased on top of the current
> 'next' branch. I have dropped the commits from Sebastian, since they
> have been merged by Sascha, and I've added one commit that fixes the
> SolidRun CuBox kwbimage.cfg to remove some lines that are no longer
> necessary after the kwbimage improvements that are introduced by this
> patch set.
>
> Best regards,
>
> Thomas
>
> Thomas Petazzoni (10):
> scripts/kwbimage: add a new function image_count_options()
> scripts/kwbimage: add a few sanity checks
> scripts/kwbimage: make the v0 image creation more flexible
> scripts/kwbimage: simplify the v1 image creation
> scripts/kwbimage: make image_boot_mode_id() return -1 on failure
> scripts/kwbimage: add support for NAND ECC and page size header
> fields
> arm: mvebu: add Feroceon CPU type
> arm: mvebu: initial support for Marvell Kirkwood SoCs
> arm: mvebu: add basic support for Globalscale Guruplug board
> arm: mvebu: remove useless lines in kwbimage.cfg for CuBox
Thomas,
I tested barebox-next with all patches applied on Dove and Armada 370.
So you get my
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
for all patches not directly related to Kirkwood (patches 7-9).
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-05-15 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 7:36 Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 01/10] scripts/kwbimage: add a new function image_count_options() Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 02/10] scripts/kwbimage: add a few sanity checks Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 03/10] scripts/kwbimage: make the v0 image creation more flexible Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 04/10] scripts/kwbimage: simplify the v1 image creation Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 05/10] scripts/kwbimage: make image_boot_mode_id() return -1 on failure Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 06/10] scripts/kwbimage: add support for NAND ECC and page size header fields Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 07/10] arm: mvebu: add Feroceon CPU type Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 08/10] arm: mvebu: initial support for Marvell Kirkwood SoCs Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 09/10] arm: mvebu: add basic support for Globalscale Guruplug board Thomas Petazzoni
2013-05-15 7:36 ` [PATCHv2 10/10] arm: mvebu: remove useless lines in kwbimage.cfg for CuBox Thomas Petazzoni
2013-05-15 20:07 ` Sebastian Hesselbarth [this message]
2013-05-17 5:41 ` [PATCHv2 00/10] kwbimage improvements, Kirkwood support Sascha Hauer
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=5193EAF6.2000605@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alior@marvell.com \
--cc=barebox@lists.infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=thomas.petazzoni@free-electrons.com \
/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