From: Zhihang Wei <wzh@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH] meta/recipes-bsp/optee-os: correct typo in class inheritance
Date: Mon, 8 Dec 2025 14:21:04 +0100 [thread overview]
Message-ID: <d8247442-9f1e-430d-a5ee-e88cb6a372f7@ilbers.de> (raw)
In-Reply-To: <20251205091419.6733-1-srinuvasan.a@siemens.com>
Applied to next, thanks.
Zhihang
On 12/5/25 10:14, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
>
> Fixed a typo that caused the optee-os class to not be inherited as expected.
>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
> meta/recipes-bsp/optee-os/optee-os-custom.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-bsp/optee-os/optee-os-custom.inc b/meta/recipes-bsp/optee-os/optee-os-custom.inc
> index 1f4ebf7e..b386047d 100644
> --- a/meta/recipes-bsp/optee-os/optee-os-custom.inc
> +++ b/meta/recipes-bsp/optee-os/optee-os-custom.inc
> @@ -5,7 +5,7 @@
> #
> # SPDX-License-Identifier: MIT
>
> -inherir optee-os
> +inherit optee-os
>
> do_warn_custom_inc() {
> bbwarn "Please migrate from \"require recipes-bsp/optee-os/optee-os-custom.inc\" to \"inherit optee-os\""
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d8247442-9f1e-430d-a5ee-e88cb6a372f7%40ilbers.de.
prev parent reply other threads:[~2025-12-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:14 srinuvasan.a via isar-users
2025-12-05 10:40 ` 'Jan Kiszka' via isar-users
2025-12-05 10:47 ` 'Jan Kiszka' via isar-users
2025-12-05 10:51 ` Srinuvasan Arjunan
2025-12-08 13:21 ` Zhihang Wei [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=d8247442-9f1e-430d-a5ee-e88cb6a372f7@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan.a@siemens.com \
/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