From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>, <u-boot@lists.denx.de>
Cc: U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 2/2] stm32mp: correct the dependency for bootcount configs
Date: Fri, 14 Jan 2022 15:26:20 +0100 [thread overview]
Message-ID: <4ef7570d-1b77-a56f-1b9f-f4091a82646e@foss.st.com> (raw)
In-Reply-To: <20211207100549.2.I6347e4b7268b9a30a04d597cd467fbcf8defd684@changeid>
Hi Patrick
On 12/7/21 10:05 AM, Patrick Delaunay wrote:
> Default value for CONFIG_SYS_BOOTCOUNT_SINGLEWORD and
> CONFIG_SYS_BOOTCOUNT_ADDR are only needed when
> CONFIG_BOOTCOUNT_GENERIC is used.
>
> This patch avoids to define these configs when an other bootcount backend
> is activated, for example for CONFIG_BOOTCOUNT_ENV.
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> ---
>
> arch/arm/mach-stm32mp/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-stm32mp/Kconfig b/arch/arm/mach-stm32mp/Kconfig
> index 2fa4ea4d5c..2819944df3 100644
> --- a/arch/arm/mach-stm32mp/Kconfig
> +++ b/arch/arm/mach-stm32mp/Kconfig
> @@ -194,7 +194,7 @@ config PRE_CON_BUF_SZ
> config BOOTSTAGE_STASH_ADDR
> default 0xC3000000
>
> -if BOOTCOUNT_LIMIT
> +if BOOTCOUNT_GENERIC
> config SYS_BOOTCOUNT_SINGLEWORD
> default y
>
>
Reviewed-by: Patrice Chotard <patrice.chotard@foss.st.com>
Thanks
Patrice
next prev parent reply other threads:[~2022-01-14 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 9:05 [PATCH 1/2] stm32mp: remove the bootcount activation Patrick Delaunay
2021-12-07 9:05 ` [PATCH 2/2] stm32mp: correct the dependency for bootcount configs Patrick Delaunay
2022-01-14 14:26 ` Patrice CHOTARD [this message]
2022-01-24 12:14 ` Patrice CHOTARD
2022-01-14 14:25 ` [PATCH 1/2] stm32mp: remove the bootcount activation Patrice CHOTARD
2022-01-24 12:14 ` Patrice CHOTARD
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=4ef7570d-1b77-a56f-1b9f-f4091a82646e@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=patrick.delaunay@foss.st.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.