[U-Boot] printf("%d") breaks u-boot 2015.01+

[Marek Vasut <marex@denx.de>]

On Monday, April 06, 2015 at 09:23:23 PM, Pavel Machek wrote:
> On Mon 2015-04-06 20:48:45, Marek Vasut wrote:
> > On Monday, April 06, 2015 at 08:14:44 PM, Pavel Machek wrote:
> > > On Mon 2015-04-06 16:59:55, Marek Vasut wrote:
> > > > On Monday, April 06, 2015 at 04:40:09 PM, Pavel Machek wrote:
> > > > > Hi!
> > > > > 
> > > > > In u-boot 2015.04-rc, as soon as execution hits printf("%d"), it
> > > > > hangs. (Usually, that's after "DRAM: " message).
> > > > 
> > > > printf("%d") expects an argument, so could it be that it touches
> > > > random piece of memory and thus hangs?
> > > 
> > > It had an argument, sorry for confusion. I was actually doing this:
> > > the test with %s works, the one with %d kills it.
> > > 
> > > I suspect too small stack...?
> > 
> > Does this happen in the SPL ? You can check the stack placement and
> > utilization with BDI to verigy your hypothesis.
> 
> No, this is u-boot proper, and I'm chainloading it (see first mail) --
> so unsupported configuration.
> 
> I'm preparing to flash the u-boot into the NOR, that should tell us if
> it is chainloading problem or not.

OK, since this email was in-reply-to SPL patch series, I got confused.
Is it in any way related to this patchset then or not ?

Best regards,
Marek Vasut