qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>
Cc: Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures
Date: Thu, 25 Apr 2019 14:43:29 +0200	[thread overview]
Message-ID: <0fdbbd5b-0ed3-0f45-8b9d-d5f5f2c76a89@redhat.com> (raw)
In-Reply-To: <20190425104326.12835-1-lersek@redhat.com>

On 4/25/19 12:43 PM, Laszlo Ersek wrote:
> Repo:      https://github.com/lersek/qemu.git
> Branch:    smbios_lp_1821884
> Launchpad: https://bugs.launchpad.net/qemu/+bug/1821884
> 
> In
> 
>   [Qemu-devel] [PATCH for 4.1 v2 09/13]
>   tests: acpi: ignore SMBIOS tests when UEFI firmware is used
> 
> at
> 
>   http://mid.mail-archive.com/1553605799-168605-10-git-send-email-imammedo@redhat.com
>   https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg07037.html
> 
> Igor had to temporarily exclude SMBIOS unit testing with UEFI guests.
> 
> Let the BiosTablesTest guest UEFI app report the SMBIOS entry point(s),
> so that SMBIOS unit tests can cover UEFI guests.
> 
> Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> 
> Thanks
> Laszlo
> 
> Laszlo Ersek (2):
>   tests/uefi-test-tools: report the SMBIOS entry point structures
>   tests/uefi-boot-images: report the SMBIOS entry point structures
> 
>  tests/uefi-test-tools/UefiTestToolsPkg/Include/Guid/BiosTablesTest.h     |  25 +++++++++++++++-----
>  tests/uefi-test-tools/UefiTestToolsPkg/BiosTablesTest/BiosTablesTest.inf |   2 ++
>  tests/uefi-test-tools/UefiTestToolsPkg/BiosTablesTest/BiosTablesTest.c   |  23 ++++++++++++++----
>  tests/data/uefi-boot-images/bios-tables-test.aarch64.iso.qcow2           | Bin 11776 -> 12288 bytes
>  tests/data/uefi-boot-images/bios-tables-test.arm.iso.qcow2               | Bin 11776 -> 11776 bytes
>  tests/data/uefi-boot-images/bios-tables-test.i386.iso.qcow2              | Bin 12800 -> 13312 bytes
>  tests/data/uefi-boot-images/bios-tables-test.x86_64.iso.qcow2            | Bin 13312 -> 13312 bytes
>  7 files changed, 40 insertions(+), 10 deletions(-)
> 

Series:
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>

  parent reply	other threads:[~2019-04-25 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 10:43 [Qemu-devel] [PATCH 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures Laszlo Ersek
2019-04-25 10:43 ` Laszlo Ersek
2019-04-25 10:43 ` [Qemu-devel] [PATCH 1/2] " Laszlo Ersek
2019-04-25 10:43   ` Laszlo Ersek
2019-04-25 11:40   ` Philippe Mathieu-Daudé
2019-04-25 11:40     ` Philippe Mathieu-Daudé
2019-05-02 14:46   ` Igor Mammedov
2019-05-02 14:46     ` Igor Mammedov
2019-04-25 10:43 ` [Qemu-devel] [PATCH 2/2] tests/uefi-boot-images: " Laszlo Ersek
2019-04-25 10:43   ` Laszlo Ersek
2019-04-25 12:43 ` Philippe Mathieu-Daudé [this message]
2019-04-25 12:43   ` [Qemu-devel] [PATCH 0/2] tests/uefi-test-tools: " Philippe Mathieu-Daudé
2019-05-02  9:16 ` Laszlo Ersek
2019-05-02  9:16   ` Laszlo Ersek
2019-05-02 14:48 ` Igor Mammedov
2019-05-02 14:48   ` Igor Mammedov

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=0fdbbd5b-0ed3-0f45-8b9d-d5f5f2c76a89@redhat.com \
    --to=philmd@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).