public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] v2013.10-rc4
Date: Wed, 09 Oct 2013 10:12:19 +0200	[thread overview]
Message-ID: <52550FE3.7020305@keymile.com> (raw)
In-Reply-To: <20131002191409.GI15917@bill-the-cat>

Hi Tom,

On 10/02/2013 09:14 PM, Tom Rini wrote:
> 
> I've put v2013.10-rc4 out, only a little later than I had hoped, but I
> wanted to get those PRs in for this.
> uploaded soon.
> 
> At this point, we're just about ready to release so:
> 1) If you have a bugfix outstand please let me know (I know about the
> igep and pcm cpsw fixes, those are on my list)
> 2) If something is broken, please shout!
> 

there are some km83xx patches outstanding for this and for the last merge
window. I guess that Kim is currently so busy that he don't find the time to
pull them.

Can you pull them directly?  Unfortunately it is a little complicated.

Patches Part one which were planned to go in for v2013.07 are already sitting in
Kims ppc83xx tree, see the lates two commits in this branch:

http://git.denx.de/?p=u-boot/u-boot-mpc83xx.git;a=shortlog;h=refs/heads/next

Patches part two are these commits:
http://patchwork.ozlabs.org/patch/256906/
http://patchwork.ozlabs.org/patch/256905/
http://patchwork.ozlabs.org/patch/256903/
http://patchwork.ozlabs.org/patch/256904/

Please note that all patches are only km board related and therefore there is no
risk at all for other boards that they get in so late.

Regards
Holger

  parent reply	other threads:[~2013-10-09  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 19:14 [U-Boot] [ANN] v2013.10-rc4 Tom Rini
2013-10-02 20:39 ` Albert ARIBAUD
2013-10-02 22:39   ` Tom Rini
2013-10-08 23:26 ` Scott Wood
2013-10-08 23:57   ` Tom Rini
2013-10-09  8:12 ` Holger Brunck [this message]
2013-10-09 14:22   ` Tom Rini

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=52550FE3.7020305@keymile.com \
    --to=holger.brunck@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