From: Tom Rini <trini@konsulko.com>
To: Daniel Palmer <daniel@thingy.jp>
Cc: visitorckw@gmail.com, angelo@kernel-space.org,
bmeng.cn@gmail.com, sjg@chromium.org, u-boot@lists.denx.de
Subject: Re: [PATCH v6 0/8] Add virtio-mmio support to m68k virt machine
Date: Thu, 14 May 2026 07:51:24 -0600 [thread overview]
Message-ID: <20260514135124.GW1858239@bill-the-cat> (raw)
In-Reply-To: <CAFr9PXkTm2ufq9cbkQQ+gPhORq-prhSf6GQP1cpjFk65+7TJKQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
On Thu, May 14, 2026 at 09:35:49PM +0900, Daniel Palmer wrote:
> Hi Tom,
>
> On Tue, 12 May 2026 at 00:00, Tom Rini <trini@konsulko.com> wrote:
> > > I didn't realise I could trigger a pipeline run so thanks for the
> > > information. Anyhow, I triggered a run for v6 and it completed and I
> > > couldn't actually find where the error in the result. I triggered it
> > > again for the v7 and it passed too. Is there something I should check
> > > before I send it again? The run is here:
> > > https://github.com/u-boot/u-boot/pull/964/checks
> >
> > That's very strange. I just re-checked v6 and still get:
> > https://source.denx.de/u-boot/u-boot/-/jobs/1446347 and both Azure and
> > Gitlab run the job the same way. Can you trigger it locally with
> > allyesconfig ?
>
> Before adding a new patch to fix the issue, building allyesconfig
> locally gave me the same error as your CI pipeline had and that went
> away when I fixed it.
Ah good, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-05-14 13:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 7:49 [PATCH v6 0/8] Add virtio-mmio support to m68k virt machine Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 1/8] sysreset: qemu virt: Use __raw_writel() Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 2/8] rtc: goldfish: Use __raw_readl() and __raw_writel() Daniel Palmer
2026-05-07 13:27 ` Simon Glass
2026-05-05 7:49 ` [PATCH v6 3/8] timer: goldfish: Use __raw_readl() Daniel Palmer
2026-05-07 13:27 ` Simon Glass
2026-05-05 7:49 ` [PATCH v6 4/8] m68k: Fix writew(), writel(), readw(), readl() endianness for classic m68k Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 5/8] virtio: mmio: Allow instantiation via platform data Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 6/8] virtio: cmd: Depend on VIRTIO_BLK Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 7/8] virtio: blk: Fix converting the vendor id to a string Daniel Palmer
2026-05-05 7:49 ` [PATCH v6 8/8] board: qemu: m68k: Create virtio mmio instances Daniel Palmer
2026-05-07 17:13 ` Kuan-Wei Chiu
2026-05-08 19:29 ` [PATCH v6 0/8] Add virtio-mmio support to m68k virt machine Tom Rini
2026-05-11 8:50 ` Daniel Palmer
2026-05-11 15:00 ` Tom Rini
2026-05-14 12:35 ` Daniel Palmer
2026-05-14 13:51 ` Tom Rini [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=20260514135124.GW1858239@bill-the-cat \
--to=trini@konsulko.com \
--cc=angelo@kernel-space.org \
--cc=bmeng.cn@gmail.com \
--cc=daniel@thingy.jp \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=visitorckw@gmail.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 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.