From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 7 Oct 2019 18:36:50 -0400 Subject: [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT In-Reply-To: <20191007175635.D9824240044@gemini.denx.de> References: <20191003072428.19197-1-patrick.delaunay@st.com> <20191007175635.D9824240044@gemini.denx.de> Message-ID: <20191007223650.GR6716@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Oct 07, 2019 at 07:56:35PM +0200, Wolfgang Denk wrote: > Dear Patrick, > > In message <20191003072428.19197-1-patrick.delaunay@st.com> you wrote: > > > > This patchset follow > > http://patchwork.ozlabs.org/project/uboot/list/?series=131268&state=* > > > > 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! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: