From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] reason: silence reason warning about CFG_INSECURE being set
Date: Tue, 25 Mar 2025 10:17:50 +0100 [thread overview]
Message-ID: <1e14eaf9-ef9f-46ed-85f3-67caa3fd4ccb@pengutronix.de> (raw)
In-Reply-To: <Z-JQTUsaIxjXOvNU@pengutronix.de>
Hello Robert,
On 3/25/25 07:42, Robert Schwebel wrote:
> On Mon, Mar 24, 2025 at 07:40:37PM +0100, Ahmad Fatoum wrote:
>> With the v2025.03 bump now in next, can you cherry-pick this patch
>> to next as well?
>
> Must have missed this, I've added the snippet to next and the warning is
> gone. Please have a look if I did it right.
The patch became only relevant with the upgrade to PTXdist >= v2025.01.0.
The applied patch to next looks fine.
Thanks,
Ahmad
>
> rsc
>
>>>>> diff --git a/configs/platform-v7a/bsp.ref b/configs/platform-v7a/bsp.ref
>>>>> index 169e555df53a..bda4db20af2c 100644
>>>>> --- a/configs/platform-v7a/bsp.ref
>>>>> +++ b/configs/platform-v7a/bsp.ref
>>>>> @@ -9,4 +9,12 @@ optee_disabled_features:
>>>>> - CFG_ENABLE_EMBEDDED_TESTS
>>>>> - CFG_TEE_CORE_TA_TRACE
>>>>>
>>>>> +optee_security_warning_disabled:
>>>>> + description: |
>>>>> + OP-TEE is used as secure monitor on STM32MP13x providing power
>>>>> + management and clock/reset control support. We don't use it as
>>>>> + part of a trusted boot setup, so it's apt for OP-TEE to warn
>>>>> + about this at startup and thus we'll keep CFG_INSECURE enabled.
>>>>> + value: True
>>>>> +
>>>>> # vim: filetype=yaml shiftwidth=2 expandtab
>
prev parent reply other threads:[~2025-03-25 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 9:59 Ahmad Fatoum
2024-12-16 14:10 ` Robert Schwebel
2024-12-16 17:17 ` Ahmad Fatoum
2025-03-24 18:40 ` Ahmad Fatoum
2025-03-25 6:42 ` Robert Schwebel
2025-03-25 9:17 ` Ahmad Fatoum [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=1e14eaf9-ef9f-46ed-85f3-67caa3fd4ccb@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=r.schwebel@pengutronix.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