All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/3] Firmware/seabios 20230912 patches
Date: Mon, 18 Sep 2023 11:59:59 +0200	[thread overview]
Message-ID: <d7zwpgvdosd7ron3odscmwfqq5cwibyqi2drkjv22z5m5nzn3r@ltokhlip4ztv> (raw)
In-Reply-To: <CAJSP0QX23UNOTCRsiHZWSa1j9KGA229S84+k7nNiDyp-AkNCFg@mail.gmail.com>

> Hi Gerd,
> I think either this pull request or your edk2 pull request causes the
> following CI failure:
> 
> >>> G_TEST_DBUS_DAEMON=/builds/qemu-project/qemu/tests/dbus-vmstate-daemon.sh QTEST_QEMU_BINARY=./qemu-system-aarch64 MALLOC_PERTURB_=199 /builds/qemu-project/qemu/build/tests/qtest/bios-tables-test --tap -k
> ――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――

Address change in ACPI tables (edk2 PR):

     DefinitionBlock ("", "SSDT", 1, "BOCHS ", "NVDIMM", 0x00000001)
     {
         Scope (\_SB)
         {
             Device (NVDR)
             {
                 Name (_HID, "ACPI0012" /* NVDIMM Root Device */)  // _HID: Hardware ID
		 [ ... ]
             }
         }
    
    -    Name (MEMA, 0x43D10000)
    +    Name (MEMA, 0x43C90000)
     }

seabios PR is fine and passes "make check".

take care,
  Gerd



  reply	other threads:[~2023-09-18 10:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 10:53 [PULL 0/3] Firmware/seabios 20230912 patches Gerd Hoffmann
2023-09-12 10:53 ` [PULL 1/3] seabios: update submodule to git snapshot Gerd Hoffmann
2023-09-12 10:53 ` [PULL 2/3] seabios: turn off CONFIG_APMBIOS for 128k build Gerd Hoffmann
2023-09-12 13:55   ` Paolo Bonzini
2023-09-18  9:50     ` Gerd Hoffmann
2023-09-12 10:53 ` [PULL 3/3] seabios: update binaries to git snapshot Gerd Hoffmann
2023-09-12 12:56 ` [PULL 0/3] Firmware/seabios 20230912 patches Stefan Hajnoczi
2023-09-18  9:59   ` Gerd Hoffmann [this message]
2023-09-18 12:52     ` Stefan Hajnoczi
2023-09-18 13:05       ` Daniel P. Berrangé
2023-09-18 13:40         ` Gerd Hoffmann

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=d7zwpgvdosd7ron3odscmwfqq5cwibyqi2drkjv22z5m5nzn3r@ltokhlip4ztv \
    --to=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.