From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: Fix bootcounter located at the end of internal SRAM
Date: Tue, 30 Oct 2018 17:59:43 +0100 [thread overview]
Message-ID: <6b375bd2-a47a-aaf5-f89a-b192890b2367@denx.de> (raw)
In-Reply-To: <5f78a742-4904-9fec-8b32-6f8d6bfa1785@denx.de>
On 10/30/2018 04:33 PM, Stefan Roese wrote:
> On 30.10.18 16:18, Marek Vasut wrote:
>>> > Of course would this be good. But perhaps we can make this SPL
>>> > binary size check "better" by not changing the INIT_RAM_SIZE
>>> > define. Its definitely possible - I just don't know how hard
>>> > (I didn't look into this).
>>>
>>> INIT_RAM_SIZE should reflect reality IMO
>>>
>>>
>>> Right. I'll check how the SPL size check works with different offsets
>>> then.
>>>
>>> So for this patch:
>>> Acked-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com
>>> <mailto:simon.k.r.goldschmidt@gmail.com>>
>>>
>>> Since this is a bugfix, will it be merged for 2018.11?
>>
>> I'll pick it if Stefan is fine with it (I guess he is) ?
>
> Yes, I am. ;)
Applied.
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2018-10-30 16:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 9:00 [U-Boot] [PATCH] arm: socfpga: Fix bootcounter located at the end of internal SRAM Stefan Roese
2018-10-30 9:07 ` Simon Goldschmidt
2018-10-30 9:36 ` Stefan Roese
2018-10-30 10:24 ` Marek Vasut
2018-10-30 10:34 ` Simon Goldschmidt
2018-10-30 11:17 ` Simon Goldschmidt
2018-10-30 11:28 ` Stefan Roese
2018-10-30 12:37 ` Simon Goldschmidt
2018-10-30 12:50 ` Stefan Roese
2018-10-30 13:02 ` Simon Goldschmidt
2018-10-30 13:13 ` Stefan Roese
2018-10-30 13:24 ` Marek Vasut
2018-10-30 15:00 ` Simon Goldschmidt
2018-10-30 15:18 ` Marek Vasut
2018-10-30 15:33 ` Stefan Roese
2018-10-30 16:59 ` Marek Vasut [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=6b375bd2-a47a-aaf5-f89a-b192890b2367@denx.de \
--to=marex@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.