Skip to content

env: Add CONFIG_ENV_FULL_SUPPORT

Tom Rini u-boot 2 versions – New

Get series with b4
b4 am 20191007223650.GR6716@bill-the-cat

Versions newest first · linked by author and title

  1. v4 Latest1 of 3 patches 0 repliesNew
  2. v30 of 3 patches 0 repliesSuperseded

1 of 3 patches is in this archive. The cover letter announces 3.

Patches in v4 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3env: correct the check of env_flags_validate presence+0 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.

Read the v4 thread

Cover letter [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT
Quoted 7 lines · Wolfgang Denk

Dear Patrick,

Quoted 4 lines · In message <[email protected]> you wrote:

This patchset follow
http://patchwork.ozlabs.org/project/uboot/list/?series=131268&state=*

Quoted 7 lines
Quoted 3 lines

It follow the first proposal
http://patchwork.ozlabs.org/project/uboot/list/?series=129339
"env: Add CONFIG_ENV_SUPPORT"

Do I understand correctly that all of this is obsolete and no longer needed after Tom's commit d90fc9c3de ``Revert "env: solve compilation error in SPL"'' ?

So, I think there's a new topic here. I seem to recall a concern from the previous thread that we could have less restrictive environment protections in SPL/TPL than we do in full U-Boot and thus open ourselves to a potential problem. As of today, U-Boot is back to where it was prior to the problematic patch being applied. But do we not have the potential problem above and thus need to evaluate the rest of the series (as the revert was largely the same as the first patch in the series) ? Thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191007/72b2bff8/attachment.sig>