From: "Marek Behún" <marek.behun@nic.cz>
To: Samuel Holland <samuel@sholland.org>
Cc: "Pali Rohár" <pali@kernel.org>,
"Andre Przywara" <andre.przywara@arm.com>,
u-boot@lists.denx.de, "Jagan Teki" <jagan@amarulasolutions.com>,
"Alex G ." <mr.nuke.me@gmail.com>,
"Artem Lapkin" <email2tema@gmail.com>,
"Priyanka Jain" <priyanka.jain@nxp.com>,
"Sughosh Ganu" <sughosh.ganu@linaro.org>
Subject: Re: [PATCH v4 1/4] tools: Separate image types which depend on OpenSSL
Date: Thu, 21 Oct 2021 14:33:55 +0200 [thread overview]
Message-ID: <20211021143355.6d979a0c@thinkpad> (raw)
In-Reply-To: <f459f316-6636-c3c5-7878-761590831d3a@sholland.org>
Hi Samuel,
On Wed, 20 Oct 2021 09:14:11 -0500
Samuel Holland <samuel@sholland.org> wrote:
> Andre is correct. No version of this patch makes *any* change to *any*
> in-tree defconfig build, because TOOLS_LIBCRYPTO=y in all defconfigs.
> Even if I was to accept your assertion that it hides a possible error on
> platforms using kwbimage:
>
> 1) It does not *create* any errors for those platforms, and
> 2) It *fixes* possible errors for almost all other platforms.
It does create possible errors, since it is possible to choose config
options which won't compile.
The fact that defconfig have this option enabled for those platforms
does not matter. What matters is that I can then validly change the
config with make menuconfig, and it won't compile. A compilation error
should not occur with valid config options. That's why dependencies
need to be made in Kconfig, so that if Kconfig decides that kwbimage is
to be built, then it will force crypto.
(Yes, I know that there currently are many ways to change Kconfig
options and the result will fail to compile. That behaviour is
unwanted and should be fixed by adding Kconfig dependencies so that it
isn't possible to choose configuration that won't compile.)
Marek
next prev parent reply other threads:[~2021-10-21 12:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 2:44 [PATCH v4 0/4] sunxi: TOC0 image type support Samuel Holland
2021-10-20 2:44 ` [PATCH v4 1/4] tools: Separate image types which depend on OpenSSL Samuel Holland
2021-10-20 7:29 ` Pali Rohár
2021-10-20 13:29 ` Andre Przywara
2021-10-20 13:47 ` Pali Rohár
2021-10-20 14:14 ` Samuel Holland
2021-10-21 12:33 ` Marek Behún [this message]
2021-10-21 13:00 ` Marek Behún
2021-10-21 13:01 ` Pali Rohár
2021-10-22 1:25 ` Samuel Holland
2021-10-22 10:09 ` Heinrich Schuchardt
2021-10-22 14:59 ` Marek Behún
2021-10-22 15:09 ` Tom Rini
2021-10-22 15:56 ` Andre Przywara
2021-10-22 16:22 ` Tom Rini
2021-10-22 16:47 ` Vagrant Cascadian
2021-10-22 17:11 ` Pali Rohár
2021-10-22 17:20 ` Andre Przywara
2021-10-22 19:46 ` Vagrant Cascadian
2021-10-27 17:11 ` Tom Rini
2021-10-27 20:11 ` Peter Robinson
2021-10-28 15:44 ` Matthias Brugger
2021-10-20 2:44 ` [PATCH v4 2/4] tools: mkimage: Add Allwinner TOC0 support Samuel Holland
2021-10-20 23:49 ` Andre Przywara
2021-10-20 2:44 ` [PATCH v4 3/4] sunxi: Support SPL in both eGON and TOC0 images Samuel Holland
2021-10-20 23:49 ` Andre Przywara
2021-10-20 2:44 ` [PATCH v4 4/4] sunxi: Support building a SPL as a TOC0 image Samuel Holland
2021-10-20 23:50 ` Andre Przywara
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=20211021143355.6d979a0c@thinkpad \
--to=marek.behun@nic.cz \
--cc=andre.przywara@arm.com \
--cc=email2tema@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=mr.nuke.me@gmail.com \
--cc=pali@kernel.org \
--cc=priyanka.jain@nxp.com \
--cc=samuel@sholland.org \
--cc=sughosh.ganu@linaro.org \
--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