From: Tom Rini <trini@konsulko.com>
To: Anurag Dutta <a-dutta@ti.com>
Cc: afd@ti.com, u-boot@lists.denx.de, a-chavda@ti.com,
u-kumar1@ti.com, nm@ti.com
Subject: Re: [PATCH 0/2] Remove "saveenv" functionality from am57xx evms
Date: Sun, 9 Feb 2025 11:20:49 -0600 [thread overview]
Message-ID: <20250209172049.GP1233568@bill-the-cat> (raw)
In-Reply-To: <20250208043938.52832-1-a-dutta@ti.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Sat, Feb 08, 2025 at 10:09:36AM +0530, Anurag Dutta wrote:
> Previously saved environment introduce discrepancies and may lead to
> incompatibilities without default settings. This series removes the saved
> environment functionality on am57xx evms so that the default configuration
> is always loaded
>
> Test result: https://gist.github.com/anuragdutta731/b253ddb0a5538ab6588a3535d7bbecf7
>
> Anurag Dutta (2):
> configs: am57xx_hs: Remove saved environments
> configs: am57xx: Remove saved environments
>
> configs/am57xx_evm_defconfig | 4 +---
> configs/am57xx_hs_evm_defconfig | 4 +---
> 2 files changed, 2 insertions(+), 6 deletions(-)
I'm not sure what this is intended to solve. A persistent environment
can be reset to the defaults with "env default -f -a" and telling users
to do this when needed when upgrading is a long standing practice.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-02-09 17:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 4:39 [PATCH 0/2] Remove "saveenv" functionality from am57xx evms Anurag Dutta
2025-02-08 4:39 ` [PATCH 1/2] configs: am57xx_hs: Remove saved environments Anurag Dutta
2025-02-08 4:39 ` [PATCH 2/2] configs: am57xx: " Anurag Dutta
2025-02-09 17:20 ` Tom Rini [this message]
2025-02-10 4:25 ` [PATCH 0/2] Remove "saveenv" functionality from am57xx evms Kumar, Udit
2025-02-10 14:43 ` Tom Rini
2025-02-19 5:03 ` Kumar, Udit
2025-02-25 17:59 ` Tom Rini
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=20250209172049.GP1233568@bill-the-cat \
--to=trini@konsulko.com \
--cc=a-chavda@ti.com \
--cc=a-dutta@ti.com \
--cc=afd@ti.com \
--cc=nm@ti.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox