From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.01-rc1 released
Date: Fri, 14 Nov 2014 11:48:33 +0100 [thread overview]
Message-ID: <5465DE01.20404@keymile.com> (raw)
In-Reply-To: <20141110212938.GX24724@bill-the-cat>
Hi Tom,
On 11/10/2014 10:29 PM, Tom Rini wrote:
> Hey all,
>
> I've pushed v2015.01-rc1 out to the repository and tarballs should exist
> soon.
>
> The merge window is now closed. Per both the min-summit and the follow
> up emails, I'm going to try and get into the every 2 week RC tagging
> groove. And, I'm going to be relying on everyones best judgement about
> what level of changes they're going to put into a pull request to me.
>
> When I do a buildman of most things I see:
> blackfin: + ip04
> arm: + Ippo_q8h_v5 novena openrd_base maxbcm openrd_ultimate openrd_client tricorder db-mv784mp-gp Linksprite_pcDuino3_fdt tricorder_flash cm_t3517
> powerpc: + kmcoge4 taishan kmlion1 dlvision
>
> And I'd really like to see those sorted out, one way or another for
> -rc2.
>
For both kmcoge4 and kmlion1, the error is fixed by [1].
Hopefully York will be able to review this, also with the 2 patches for the
migration of the keymile powerpc board to generic board, for -rc2.
Best Regards
Valentin
[1] http://patchwork.ozlabs.org/patch/403232/
prev parent reply other threads:[~2014-11-14 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 21:29 [U-Boot] [ANN] U-Boot v2015.01-rc1 released Tom Rini
2014-11-11 10:44 ` Masahiro Yamada
2014-11-12 9:12 ` Andreas Bießmann
2014-11-12 17:04 ` Tom Rini
2014-11-12 21:10 ` Tom Rini
2014-11-12 22:16 ` Tom Rini
2014-11-13 15:34 ` Tom Rini
2014-11-12 18:24 ` Nikita Kiryanov
2014-11-12 18:54 ` Tom Rini
2014-11-13 9:46 ` Stefano Babic
2014-11-13 10:06 ` Marek Vasut
2014-11-13 15:15 ` Dirk Eibach
2014-11-14 10:48 ` Valentin Longchamp [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=5465DE01.20404@keymile.com \
--to=valentin.longchamp@keymile.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