From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jerome Forissier <jerome.forissier@linaro.org>, u-boot@lists.denx.de
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Jerome Forissier <jerome.forissier@linaro.org>,
Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
Stefan Roese <sr@denx.de>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Joshua Watt <jpewhacker@gmail.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH] Make AVB_VERIFY depend on FASTBOOT
Date: Tue, 08 Oct 2024 15:15:12 +0200 [thread overview]
Message-ID: <87cykag2hr.fsf@baylibre.com> (raw)
In-Reply-To: <20241002144845.1439316-1-jerome.forissier@linaro.org>
Hi Jerome,
Thank you for the patch.
On mer., oct. 02, 2024 at 16:48, Jerome Forissier <jerome.forissier@linaro.org> wrote:
> AVB_BUF_ADDR, which is under "if AVB_VERIFY", defaults to
> FASTBOOT_BUF_ADDR. Therefore AVB_VERIFY should depend on FASTBOOT.
>
> Signed-off-by: Jerome Forissier <jerome.forissier@linaro.org>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> ---
> common/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/common/Kconfig b/common/Kconfig
> index 957de0c5c02..c011ab6e820 100644
> --- a/common/Kconfig
> +++ b/common/Kconfig
> @@ -850,6 +850,7 @@ config AVB_VERIFY
> depends on LIBAVB
> depends on MMC
> depends on PARTITION_UUIDS
> + depends on FASTBOOT
> help
> This option enables compilation of bootloader-dependent operations,
> used by Android Verified Boot 2.0 library (libavb). Includes:
> --
> 2.40.1
next prev parent reply other threads:[~2024-10-08 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 14:48 [PATCH] Make AVB_VERIFY depend on FASTBOOT Jerome Forissier
2024-10-08 13:15 ` Mattijs Korpershoek [this message]
2024-10-11 12:32 ` Mattijs Korpershoek
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=87cykag2hr.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=jpewhacker@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=rasmus.villemoes@prevas.dk \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=trini@konsulko.com \
--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