From: Philippe REYNES <philippe.reynes@softathome.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH] bootcount: add support to customize bootcount variable name
Date: Mon, 9 Sep 2019 18:41:02 +0200 (CEST) [thread overview]
Message-ID: <992029351.2212296.1568047262683.JavaMail.zimbra@softathome.com> (raw)
In-Reply-To: <20190909160627.7E86A24003E@gemini.denx.de>
Hi Wolfgang,
> Dear Philippe,
>
> In message <1568037413-28155-1-git-send-email-philippe.reynes@softathome.com>
> you wrote:
>> This commit add an option to customize the bootcount variable
>> name in the u-boot environment. To stay compatible with old config,
>> the default name is bootcount.
>
> Which exact problem are you trying to fix with this commit?
I have severals layers in my boot chain, and I want to use bootcount
in severals layers to manage boot issues. If severals layers use the
same variable name (bootcount) and a boot issue happen, I can't find
the layer that fails.
So I propose to "customize" the bootcount variable name.
> I mean, we have a ton of variable names with fixed meaning, which
> have been in use for nearly 2 decades - bootcmd, bootargs,
> bootcount, ...
>
> What is wrong with the "boootcount" name?
As it is "unique", I can't chain severals bootcount.
That's why I propose an option to customize the bootcount name variable.
I know that it's a "corner case" and that you could prefer to avoid
adding another option, that's why I've proposed this option as a RFC.
> Best regards,
>
> Wolfgang Denk
Best regards,
Philippe Reynes
next prev parent reply other threads:[~2019-09-09 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 13:56 [U-Boot] [RFC][PATCH] bootcount: add support to customize bootcount variable name Philippe Reynes
2019-09-09 16:06 ` Wolfgang Denk
2019-09-09 16:41 ` Philippe REYNES [this message]
2019-09-10 8:23 ` Wolfgang Denk
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=992029351.2212296.1568047262683.JavaMail.zimbra@softathome.com \
--to=philippe.reynes@softathome.com \
--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