From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.11-rc2 released
Date: Tue, 18 Oct 2016 07:02:03 +0200 [thread overview]
Message-ID: <5805ACCB.10708@denx.de> (raw)
In-Reply-To: <20161018001538.GY18591@bill-the-cat>
Hello Tom,
Am 18.10.2016 um 02:15 schrieb Tom Rini:
> Hey all,
>
> It's release day and v2016.11-rc2 is out. I've tried to clean up my
> queue a bit, but I think there's still a few things I have outstanding.
> And I know I need to get some changes from Alexander for EFI stuff that
> I've already promised can come in. But we should also be moving towards
> release.
>
> So I will be picking up some Kconfig related changes and making sure we
> have no (unexplained) binary size changes.
>
> A perhaps less obvious change between -rc1 and -rc2 is that I've added
> test.py running for qemu-ppce500, qemu-x86, vexpress_ca15_tc2,
> vexpres_ca9x5 and integratorap_cm926ejs along with qemu-mips*.
>
> I plan on doing -rc3 on the 31st.
Thanks!
rc2 is working on
powerpc TQM5200 board
http://xeidos.ddns.net/tests/test_db_auslesen.php#132
am335x shc:
http://xeidos.ddns.net/tests/test_db_auslesen.php#135
at91 corvus and smartweb board:
(The automated build fails, as I apply local patches, one failed with
rc2 ... fixed it, as similiar patch is now in mainline, so I had
to start the builds manually for the 2 boards)
http://xeidos.ddns.net/tests/test_db_auslesen.php#137
http://xeidos.ddns.net/tests/test_db_auslesen.php#138
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-10-18 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 0:15 [U-Boot] [ANN] U-Boot v2016.11-rc2 released Tom Rini
2016-10-18 5:02 ` Heiko Schocher [this message]
2016-10-18 8:45 ` Peter Robinson
2016-10-21 1:52 ` Masahiro Yamada
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=5805ACCB.10708@denx.de \
--to=hs@denx.de \
--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.