From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] common: add help text for CONFIG_STATE
Date: Thu, 9 Jun 2022 10:50:10 +0200 [thread overview]
Message-ID: <20220609085010.GJ1615@pengutronix.de> (raw)
In-Reply-To: <20220609060923.670163-1-a.fatoum@pengutronix.de>
On Thu, Jun 09, 2022 at 08:09:23AM +0200, Ahmad Fatoum wrote:
> While we have extensive documentation for state, some sentences in the
> kconfig are a good thing.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> v1 -> v2:
> - remove reference to barebox TLV until that support is upstreamed.
> ---
> common/Kconfig | 5 +++++
> 1 file changed, 5 insertions(+)
Applied, thanks
Sascha
>
> diff --git a/common/Kconfig b/common/Kconfig
> index f7a6a96e877c..3ff45d6c9d0d 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -1004,6 +1004,11 @@ config STATE
> select ENVIRONMENT_VARIABLES
> select OFTREE
> select PARAMETER
> + help
> + barebox state is a generic framework for atomic power fail-safe
> + variable storage and retrieval. It can be used to safely maintain
> + data over reboots and to exchange information with Linux, e.g.
> + for redundant boot with bootchooser.
>
> config STATE_CRYPTO
> bool "HMAC based authentication support"
> --
> 2.30.2
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2022-06-09 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 6:09 Ahmad Fatoum
2022-06-09 8:50 ` Sascha Hauer [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=20220609085010.GJ1615@pengutronix.de \
--to=sha@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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