From: Tom Rini <trini@konsulko.com>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 1/2] efi_stub: Sync the debug UART definition like other platform
Date: Thu, 28 Nov 2024 21:28:58 -0600 [thread overview]
Message-ID: <20241129032858.GG3600562@bill-the-cat> (raw)
In-Reply-To: <35abc74c-0936-40db-b574-da3bec78bea5@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On Fri, Nov 29, 2024 at 11:22:50AM +0800, Kever Yang wrote:
> Hi Tom, Simon,
>
> With these two patches, I didn't see error report in efi_stub for
> disable DEBUG_UART,
>
> but I still get CI build error below, but I can't identify what's the
> problem, could you help to take a look:
>
> https://source.denx.de/u-boot/custodians/u-boot-rockchip/-/jobs/963215
So, with:
88 60 2 /150 qemu-x86_64
We know two boards failed to build. I don't know why buildman
doesn't then list them as part of the summary, and please file an issue
in Gitlab for Simon for that. However, we can try and figure it out by:
./tools/buildman/buildman -o /tmp -PEWM -x arm,powerpc --dry-run -v
In that tree, and seeing what's listed there but not in the CI output
summary.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-11-29 3:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 3:47 [PATCH 1/2] efi_stub: Sync the debug UART definition like other platform Kever Yang
2024-11-28 3:47 ` [PATCH 2/2] config: efi-x86_payload: Enable DEBUG_UART Kever Yang
2025-01-03 16:16 ` Heinrich Schuchardt
2025-01-04 1:11 ` Heinrich Schuchardt
2025-01-04 19:29 ` Simon Glass
2025-01-04 23:02 ` Heinrich Schuchardt
2025-01-06 6:46 ` Kever Yang
2025-01-06 12:40 ` Simon Glass
2025-01-06 22:04 ` Tom Rini
2024-11-29 3:22 ` [PATCH 1/2] efi_stub: Sync the debug UART definition like other platform Kever Yang
2024-11-29 3:28 ` Tom Rini [this message]
2024-12-09 13:28 ` Simon Glass
2025-01-03 15:43 ` Heinrich Schuchardt
2025-01-06 3:33 ` Kever Yang
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=20241129032858.GG3600562@bill-the-cat \
--to=trini@konsulko.com \
--cc=ilias.apalodimas@linaro.org \
--cc=kever.yang@rock-chips.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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