From: Ian Abbott <abbotti@mev.co.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Setting MAC address from nv variable broken in barebox 2017.05.0?
Date: Thu, 11 May 2017 10:48:38 +0100 [thread overview]
Message-ID: <aa3c66bb-4ed5-93f7-c339-399d423b878d@mev.co.uk> (raw)
In-Reply-To: <20170511061719.73uskd22dpy7v2av@pengutronix.de>
On 11/05/17 07:17, Sascha Hauer wrote:
> On Tue, May 09, 2017 at 11:02:12AM +0100, Ian Abbott wrote:
>> While on the subject, what is the desired behaviour when removing an nv
>> variable? Currently, removing an nv variable also deletes a global with the
>> same name, even if the global has changed value in the meantime:
>>
>> barebox@xxxx:/ global -r quux
>> barebox@xxxx:/ nv -r quux
>> barebox@xxxx:/ nv quux=foo
>> barebox@xxxx:/ global quux=bar
>> barebox@xxxx:/ nv -r quux
>> barebox@xxxx:/ global
>> ... list of globals but 'quux' is missing ...
>>
>> In 2017-04-0, the global variable remained, although its value was cleared.
>
> Are you sure the global variable is removed? I can't reproduce this
> here. Here the globalvar is cleared as it used to be. However, this
> behaviour is not very nice and could be changed with the following
> patch.
Sorry, my mistake. You are correct, the global var remains but is cleared.
--
-=( 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
prev parent reply other threads:[~2017-05-11 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 13:39 Ian Abbott
2017-05-08 14:34 ` Sascha Hauer
2017-05-08 15:44 ` Ian Abbott
2017-05-08 14:45 ` Ian Abbott
2017-05-08 14:49 ` Ian Abbott
2017-05-08 18:12 ` Sascha Hauer
2017-05-09 10:02 ` Ian Abbott
2017-05-11 6:17 ` Sascha Hauer
2017-05-11 9:48 ` 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=aa3c66bb-4ed5-93f7-c339-399d423b878d@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