From: Quentin Schulz <quentin.schulz@cherry.de>
To: Marek Vasut <marex@denx.de>, u-boot@lists.denx.de
Cc: Dragan Simic <dsimic@manjaro.org>,
Joe Hershberger <joe.hershberger@ni.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH v2] env: mmc: Make redundant env in both eMMC boot partitions consider DT properties
Date: Tue, 11 Feb 2025 17:39:05 +0100 [thread overview]
Message-ID: <a84495fa-c4dc-4404-9bba-fb83c228a3a5@cherry.de> (raw)
In-Reply-To: <6d6d0241-9be7-4b1c-bd45-98fa50cf5d65@denx.de>
Hi Marek,
On 2/11/25 5:06 PM, Marek Vasut wrote:
> On 2/11/25 2:47 PM, Quentin Schulz wrote:
>
> Hi,
>
>>> + if (CONFIG_SYS_MMC_ENV_PART != 1)
>>
>> Oof what a terrible name for the actual meaning :/
>>
>> MMC hardware partition device number on the platform where the
>> environment is stored. Note that this is not related to
>> any software
>> defined partition table but instead if we are in the user
>> area, which is
>> partition 0 or the first boot partition, which is 1 or some
>> other defined
>> partition.
>>
>> Would benefit from a small comment making this less confusing in the
>> code.
>
> Maybe CONFIG_SYS_MMC_ENV_PART should be renamed instead ... to some
> CONFIG_ENV_MMC_HW_PART
>
config ENV_MMC_IN_BOOT_PART
bool "env in eMMC boot partition"
help
Store the environment in eMMC boot partition (y) or in user
partition (n).
Maybe?
Out of scope for this patch though :)
Cheers,
Quentin
next prev parent reply other threads:[~2025-02-11 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 13:31 [PATCH v2] env: mmc: Make redundant env in both eMMC boot partitions consider DT properties Marek Vasut
2025-02-11 13:47 ` Quentin Schulz
2025-02-11 16:06 ` Marek Vasut
2025-02-11 16:39 ` Quentin Schulz [this message]
2025-02-13 8:30 ` Mattijs Korpershoek
2025-02-18 22:31 ` 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=a84495fa-c4dc-4404-9bba-fb83c228a3a5@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=dsimic@manjaro.org \
--cc=joe.hershberger@ni.com \
--cc=marex@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 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.