From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] env: env_sf: don't set .init op if not needed
Date: Sun, 08 Nov 2020 14:25:25 +0100 [thread overview]
Message-ID: <541405.1604841925@gemini.denx.de> (raw)
In-Reply-To: <20201106204557.GG5340@bill-the-cat>
Dear Tom,
In message <20201106204557.GG5340@bill-the-cat> you wrote:
>
> > Later (208bd2b8), _NOWHERE was made non-mutually-exclusive with the real
> > storage targets.
>
> Yes. It's intentional that "NOWHERE" means that if this is our run-time
> location for the environment, then you cannot save the environment. But
> since we finally implemented the ability to have more than one option
> enabled and pick the correct one at run time, we build both "mmc" and
> "nowhere".
But this breaks logic. If you wanna have a nulldev, than implement
a /dev/null.
CONFIG_ENV_IS_NOWHERE should be the means to be used when no
environment storage drivers are needed / selected, not even
/dev/null.
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
My challenge to the goto-less programmer is to recode tcp_input()
without any gotos ... without any loss of efficiency (there has to be
a catch). - W. R. Stevens
next prev parent reply other threads:[~2020-11-08 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 13:38 [PATCH] env: env_sf: don't set .init op if not needed Michael Walle
2020-11-02 7:00 ` Heiko Schocher
2020-11-02 12:51 ` Wolfgang Denk
2020-11-03 5:15 ` Heiko Schocher
2020-11-03 7:52 ` Wolfgang Denk
2020-11-03 9:42 ` Rasmus Villemoes
2020-11-05 16:40 ` Wolfgang Denk
2020-11-06 7:46 ` Rasmus Villemoes
2020-11-06 20:45 ` Tom Rini
2020-11-08 13:25 ` Wolfgang Denk [this message]
2020-11-08 13:22 ` Wolfgang Denk
2020-11-02 20:15 ` Michael Walle
2020-11-03 4:40 ` Heiko Schocher
2020-11-03 12:30 ` 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=541405.1604841925@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