mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>,
	Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] globalvar: Fix value of new globalvar when nvvar exists
Date: Tue, 9 May 2017 10:43:32 +0100	[thread overview]
Message-ID: <bb74302d-ee13-77af-fccc-351e93bee0c4@mev.co.uk> (raw)
In-Reply-To: <20170508181031.25106-1-s.hauer@pengutronix.de>

On 08/05/17 19:10, Sascha Hauer wrote:
> When a new globalvar with a value is created and the corresponding
> nvvar exists, then the globalvar gets the value of the nvvar, not
> from the newly assigned value as expected.
>
> nv quux=foo; global quux=bar; echo ${global.quux}
>
> Should give "bar", not "foo". Fix this.
>
> Reported-by: Ian Abbott <abbotti@mev.co.uk>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
>  common/globalvar.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/common/globalvar.c b/common/globalvar.c
> index c48e7df067..c528b24062 100644
> --- a/common/globalvar.c
> +++ b/common/globalvar.c
> @@ -403,11 +403,11 @@ int globalvar_add_simple(const char *name, const char *value)
>  			return PTR_ERR(param);
>  	}
>
> +	globalvar_nv_sync(name);
> +
>  	if (value)
>  		dev_set_param(&global_device, name, value);
>
> -	globalvar_nv_sync(name);
> -
>  	return 0;
>  }

This seems to work.  Thanks.

-- 
-=( Ian Abbott @ MEV Ltd.    E-mail: <abbotti@mev.co.uk> )=-
-=(                          Web: http://www.mev.co.uk/  )=-

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2017-05-09  9:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08 18:10 Sascha Hauer
2017-05-09  9:43 ` Ian Abbott [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=bb74302d-ee13-77af-fccc-351e93bee0c4@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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