From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] v2013.01-rc3 out
Date: Mon, 14 Jan 2013 07:47:54 -0500 [thread overview]
Message-ID: <50F3FE7A.6070909@ti.com> (raw)
In-Reply-To: <50F3B4B4.9070208@compulab.co.il>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/14/2013 02:33 AM, Nikita Kiryanov wrote:
> On 01/10/2013 11:49 PM, Tom Rini wrote:
>> Hey all,
>>
>> As a reminder, we're scheduled for v2013.01 on the 15th. I've
>> pushed out v2013.01-rc3 now. I still expect: - At least one more
>> u-boot-arm PR - Any other outstand bug fixes
>>
>> I saw there was a request for an m68k change to come in from a
>> developer, Jason can you review and pass along please? It is
>> assigned to you in patchwork. And I suspect there's a few more
>> bugfixes out there we need to handle (I know of 2 different one
>> for IGEP boards).
>>
>> Please remind me here if there's something else that needs
>> reviewing and going in, thanks!
>>
>>
>
> Any chance of including my card detect and write protection series
> for omap mmc (omap mmc: implement card detect and write
> protection)? We really want this in the next release and it looks
> like Andy is away, so he probably won't respond to it in time.
It came in well past the merge window closure, sorry. It should be in
the next release.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJQ8/56AAoJENk4IS6UOR1WUwwP/3hL/COzQ+r5RNTpobyV+EcA
YIhNaIp6VtuWl/CtuH35Yi9NMPRoWcXXgKrADhWW4GTpELpeM12oKAf4pbUVSsS/
YlzurpyWyQ8Sm0+aqvc/xlacoD9XOQHlwnYh6bK3hgDB8easW9VO9UJr6rKVMrQy
To9hN0C48OwUCM1RB55E4XloCOk5VjBu4k6LBTo714oYXXDGypXqirne2GKHOHPT
YHK10Dt0c+AYKmmy+gdMHYYoYIz4VxoLYmy28NGI1pbmKc7/PcABu8qo1iAc4oUI
Gtxa9sLbf49wubqNwixcNGV120X2uUX/1s6d+1RxW4+akgnjgsihAQF0aL4zSMBA
g7qKP0pBYAlpk6ioaUnAFzXsR1XZ1rDLTz9u+sBPYu1ob9mohNzpmop2L7Oo7VF1
35HU75qHBN/TDg9Ks3Eb2DzBzbAR18Z7G2aByefMgL0BV9sO9eP/pz41aN6itbOV
X28UEk0avC5nUATuiOr+1tWKASniCTJXu89UQM2LrzlfBGw0B8B7m5u6sRxurCND
M0+h7ULCIrgUtpA0CKfKEIrIFuC98VwLTtJk4ThMVG5Vp3Vz/XJWm3taXai3NpR0
Gezc4RNnS5Nps85waa79le3UzNts6P4QsE09TFKLByYXTeApAW3uy3vj0QB0ckVl
6Snxx2PAt0M2oVNiKlbF
=1onC
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-01-14 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 21:49 [U-Boot] [STATUS] v2013.01-rc3 out Tom Rini
2013-01-11 7:15 ` Lukasz Majewski
2013-01-11 13:27 ` Marek Vasut
2013-01-11 14:49 ` Jens Scharsig
2013-01-14 7:33 ` Nikita Kiryanov
2013-01-14 12:47 ` Tom Rini [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=50F3FE7A.6070909@ti.com \
--to=trini@ti.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.