From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2016.01-rc2 released
Date: Mon, 15 Feb 2016 17:49:23 -0500 [thread overview]
Message-ID: <20160215224923.GO23166@bill-the-cat> (raw)
Hey all,
I've pushed v2016.01-rc2 out to the repository and tarballs should exist
soon.
I've picked up a number of odds and ends and PRs for this rc. I think
things are looking good. If there's something I should have picked up,
but haven't, please speak up now.
For example, I'm not quite sure if everyone is happy yet with the EFI
patches, but I'd like them in too. And I think we need at least a v2 of
some parts of the FIT+SPL patches.
As always, if anything is broken please speak up.
Thanks all!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160215/c9b6bdc0/attachment.sig>
next reply other threads:[~2016-02-15 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 22:49 Tom Rini [this message]
2016-02-16 7:25 ` [U-Boot] [ANN] U-Boot v2016.01-rc2 released Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2015-12-07 19:27 Tom Rini
2015-12-07 20:12 ` Wolfgang Denk
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=20160215224923.GO23166@bill-the-cat \
--to=trini@konsulko.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