From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Ross Burton <Ross.Burton@arm.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH v3 5/5] oeqa parselogs: add parselogs-ignores-genericarm64.txt
Date: Fri, 11 Jul 2025 12:30:13 +0300 [thread overview]
Message-ID: <aHDZpReCMhrztS7a@nuoska> (raw)
In-Reply-To: <184E5E78D990934F.30429@lists.yoctoproject.org>
Hi Ross and Richard,
Enablers for this have been merged to poky master branch now.
Could this be applied too?
I've noticed that meta-yocto-bsp patched are not getting applied
like changes to oe-core. Is there something wrong with the changes
or is something different in the review process which I could
take into account?
Cheers,
-Mikko
On Wed, Jul 02, 2025 at 10:25:59AM +0300, Mikko Rapeli via lists.yoctoproject.org wrote:
> With safe to ignore pinctl and initrd warnings from
> AMD kv260 boot.
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
> .../lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt | 4 ++++
> 1 file changed, 4 insertions(+)
> create mode 100644 meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
>
> diff --git a/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt b/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
> new file mode 100644
> index 000000000000..1e8b1f4b7d1b
> --- /dev/null
> +++ b/meta-yocto-bsp/lib/oeqa/runtime/cases/parselogs-ignores-genericarm64.txt
> @@ -0,0 +1,4 @@
> +# safe to ignore minor firmware issue
> +zynqmp-pinctrl firmware:zynqmp-firmware:pinctrl: failed to set: pin
> +# safe to ignore initrd warning
> +Can't lookup blockdev
> --
> 2.43.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#13690): https://lists.yoctoproject.org/g/poky/message/13690
> Mute This Topic: https://lists.yoctoproject.org/mt/113944197/7159507
> Group Owner: poky+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/poky/unsub [mikko.rapeli@linaro.org]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next parent reply other threads:[~2025-07-11 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <184E5E78D990934F.30429@lists.yoctoproject.org>
2025-07-11 9:30 ` Mikko Rapeli [this message]
2025-07-11 13:07 ` [poky] [PATCH v3 5/5] oeqa parselogs: add parselogs-ignores-genericarm64.txt Richard Purdie
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=aHDZpReCMhrztS7a@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=Ross.Burton@arm.com \
--cc=poky@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.