qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PULL 6/6] tests/acpi: disallow tests/data/acpi/virt/SSDT.memhp changes
Date: Wed, 13 Dec 2023 09:33:05 -0500	[thread overview]
Message-ID: <20231213093242-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <AD96681F-FBF0-4AB9-8F2B-5B6C1FB5A52F@redhat.com>

On Wed, Dec 13, 2023 at 04:24:24PM +0530, Ani Sinha wrote:
> 
> 
> > On 13-Dec-2023, at 4:20 PM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > 
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> 
> Please combine this patch with patch 5. No need to do this separately.


Yes but since it's done - it's fine either way I think. No?

> > ---
> > tests/qtest/bios-tables-test-allowed-diff.h | 1 -
> > 1 file changed, 1 deletion(-)
> > 
> > diff --git a/tests/qtest/bios-tables-test-allowed-diff.h b/tests/qtest/bios-tables-test-allowed-diff.h
> > index e569098abddc..dfb8523c8bf4 100644
> > --- a/tests/qtest/bios-tables-test-allowed-diff.h
> > +++ b/tests/qtest/bios-tables-test-allowed-diff.h
> > @@ -1,2 +1 @@
> > /* List of comma-separated changed AML files to ignore */
> > -"tests/data/acpi/virt/SSDT.memhp",
> > -- 
> > 2.43.0
> > 



  reply	other threads:[~2023-12-13 14:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 10:50 [PULL 0/6] Firmware/edk2 20231213 patches Gerd Hoffmann
2023-12-13 10:50 ` [PULL 1/6] tests/acpi: allow tests/data/acpi/virt/SSDT.memhp changes Gerd Hoffmann
2023-12-13 10:50 ` [PULL 2/6] edk2: update to git snapshot Gerd Hoffmann
2023-12-13 10:50 ` [PULL 3/6] edk2: update build config, set PcdUninstallMemAttrProtocol = TRUE Gerd Hoffmann
2023-12-13 10:50 ` [PULL 5/6] tests/acpi: update expected data files Gerd Hoffmann
2023-12-13 10:50 ` [PULL 6/6] tests/acpi: disallow tests/data/acpi/virt/SSDT.memhp changes Gerd Hoffmann
2023-12-13 10:54   ` Ani Sinha
2023-12-13 14:33     ` Michael S. Tsirkin [this message]
2023-12-13 14:39       ` Ani Sinha
2023-12-13 15:03         ` Michael S. Tsirkin
2023-12-13 15:14           ` Gerd Hoffmann
2023-12-13 15:17             ` Michael S. Tsirkin
2023-12-13 15:22               ` Ani Sinha
2024-01-11 14:01 ` [PULL 0/6] Firmware/edk2 20231213 patches Gerd Hoffmann
2024-01-11 15:52   ` Peter Maydell
2024-01-11 16:02     ` Peter Maydell
2024-01-11 16:28       ` Gerd Hoffmann
2024-01-12 12:47         ` Peter Maydell
2024-01-12 16:19           ` Peter Maydell
2024-01-12 16:19             ` Peter Maydell
2024-01-15 10:20             ` Gerd Hoffmann
2024-01-17 10:16               ` Michael Tokarev
2024-01-17 14:29                 ` Gerd Hoffmann
2024-01-18 12:56                   ` Peter Maydell
2024-01-12 14:27         ` Michael Tokarev
2024-01-12 14:30           ` Michael Tokarev

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=20231213093242-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@linaro.org \
    --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).