public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cosmetic: fix CONFIG_SPL_BSS_MAX_SIZE typo in README
Date: Sun, 14 Apr 2013 16:51:26 +0200	[thread overview]
Message-ID: <20130414165126.3fe0e4ac@lilith> (raw)
In-Reply-To: <1365950918-26499-1-git-send-email-albert.u.boot@aribaud.net>

Hi Albert,

On Sun, 14 Apr 2013 16:48:38 +0200, Albert ARIBAUD
<albert.u.boot@aribaud.net> wrote:

> 
> Signed-off-by: Albert ARIBAUD <albert.u.boot@aribaud.net>
> ---
>  README |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/README b/README
> index 19da9c8..0bc0af5 100644
> --- a/README
> +++ b/README
> @@ -2835,7 +2835,7 @@ FIT uImage format:
>  		Maximum size in memory allocated to the SPL, BSS included.
>  		When defined, the linker checks that the actual memory
>  		used by SPL from _start to __bss_end does not exceed it.
> -		CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_MAX_BSS_SIZE
> +		CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
>  		must not be both defined at the same time.
>  
>  		CONFIG_SPL_MAX_SIZE
> @@ -2858,7 +2858,7 @@ FIT uImage format:
>  		Maximum size in memory allocated to the SPL BSS.
>  		When defined, the linker checks that the actual memory used
>  		by SPL from __bss_start to __bss_end does not exceed it.
> -		CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_MAX_BSS_SIZE
> +		CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
>  		must not be both defined at the same time.
>  
>  		CONFIG_SPL_STACK

Beno?t, is this OK? If so, I'll apply it on ARM.

Amicalement,
-- 
Albert.

  reply	other threads:[~2013-04-14 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 14:48 [U-Boot] [PATCH] cosmetic: fix CONFIG_SPL_BSS_MAX_SIZE typo in README Albert ARIBAUD
2013-04-14 14:51 ` Albert ARIBAUD [this message]
2013-04-14 14:50   ` Benoît Thébaudeau
2013-04-14 14:59 ` Albert ARIBAUD

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=20130414165126.3fe0e4ac@lilith \
    --to=albert.u.boot@aribaud.net \
    --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