From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT
Date: Mon, 07 Oct 2019 19:56:35 +0200 [thread overview]
Message-ID: <20191007175635.D9824240044@gemini.denx.de> (raw)
In-Reply-To: <20191003072428.19197-1-patrick.delaunay@st.com>
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"'' ?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The scientists of today think deeply instead of clearly. One must be
sane to think clearly, but one can think deeply and be quite insane.
- Nikola Tesla
next prev parent reply other threads:[~2019-10-07 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 7:24 [U-Boot] [PATCH v4 0/3] env: Add CONFIG_ENV_FULL_SUPPORT Patrick Delaunay
2019-10-03 7:24 ` [U-Boot] [PATCH v4 1/3] env: correct the check of env_flags_validate presence Patrick Delaunay
2019-10-03 13:18 ` Tom Rini
2019-10-03 7:24 ` [U-Boot] [PATCH v4 2/3] env: introduce macro ENV_IS_IN_SOMEWHERE Patrick Delaunay
2020-03-18 16:03 ` Patrick DELAUNAY
2019-10-03 7:24 ` [U-Boot] [PATCH v4 3/3] env: Add CONFIG_ENV_FULL_SUPPORT Patrick Delaunay
2020-03-18 16:06 ` Patrick DELAUNAY
2019-10-07 17:56 ` Wolfgang Denk [this message]
2019-10-07 22:36 ` [U-Boot] [PATCH v4 0/3] " Tom Rini
2019-10-08 11:09 ` Wolfgang Denk
2019-10-14 14:46 ` Patrick DELAUNAY
2019-10-15 9:28 ` Wolfgang Denk
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=20191007175635.D9824240044@gemini.denx.de \
--to=wd@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox