From: Neil Armstrong <neil.armstrong@linaro.org>
To: Alexey Romanov <avromanov@salutedevices.com>, narmstrong@baylibre.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de, kernel@sberdevices.ru
Subject: Re: [PATCH v1] drivers: don't compile Secure Monitor UCLASS unconditionally
Date: Sun, 15 Oct 2023 12:30:40 +0200 [thread overview]
Message-ID: <25322756-2d1a-f14d-134b-8e394f2979d3@linaro.org> (raw)
In-Reply-To: <20231013130411.46569-1-avromanov@salutedevices.com>
Le 13/10/2023 à 15:04, Alexey Romanov a écrit :
> It makes no sense to compile Secure Monitor unconditionally.
> For example, this break the SPL build on boards with a small
> allowed SPL image size.
>
> Fixes: 126fbbefd89e ("drivers: introduce Secure Monitor uclass")
>
> Signed-off-by: Alexey Romanov <avromanov@salutedevices.com>
> ---
> drivers/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/Makefile b/drivers/Makefile
> index b7bd3633b1..1a768fed2b 100644
> --- a/drivers/Makefile
> +++ b/drivers/Makefile
> @@ -34,6 +34,7 @@ obj-$(CONFIG_$(SPL_TPL_)VIRTIO) += virtio/
> obj-$(CONFIG_$(SPL_)DM_MAILBOX) += mailbox/
> obj-$(CONFIG_$(SPL_)REMOTEPROC) += remoteproc/
> obj-$(CONFIG_$(SPL_)SYSINFO) += sysinfo/
> +obj-$(CONFIG_$(SPL_TPL_)SM) += sm/
> obj-$(CONFIG_$(SPL_TPL_)TPM) += tpm/
> obj-$(CONFIG_XEN) += xen/
> obj-$(CONFIG_$(SPL_)FPGA) += fpga/
> @@ -124,4 +125,3 @@ obj-$(CONFIG_DM_RNG) += rng/
> endif
>
> obj-y += soc/
> -obj-y += sm/
Thanks, squashed into 126fbbefd89e ("drivers: introduce Secure Monitor uclass")
Neil
prev parent reply other threads:[~2023-10-15 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 13:04 [PATCH v1] drivers: don't compile Secure Monitor UCLASS unconditionally Alexey Romanov
2023-10-14 18:19 ` Simon Glass
2023-10-15 10:30 ` Neil Armstrong [this message]
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=25322756-2d1a-f14d-134b-8e394f2979d3@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=avromanov@salutedevices.com \
--cc=kernel@sberdevices.ru \
--cc=narmstrong@baylibre.com \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).