From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Jonathan Cameron via <qemu-devel@nongnu.org>,
ani@anisinha.ca, berrange@redhat.com, Fan Ni <fan.ni@samsung.com>,
Dave Jiang <dave.jiang@intel.com>
Subject: Re: [RFC PATCH 0/4] hw/i386: Factor out PXB parts of DSDT into an SSDT table
Date: Tue, 11 Apr 2023 10:05:01 -0400 [thread overview]
Message-ID: <20230411100416-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230411160219.64f0aa2f@imammedo.users.ipa.redhat.com>
On Tue, Apr 11, 2023 at 04:02:19PM +0200, Igor Mammedov wrote:
> PS2:
> Also, I'm working on expanding PCI slots descriptors to PXBs,
> and more or less that will negate this tables split.
Hmm any ETA? We can defer this discussion until after that is posted.
--
MST
next prev parent reply other threads:[~2023-04-11 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 16:54 [RFC PATCH 0/4] hw/i386: Factor out PXB parts of DSDT into an SSDT table Jonathan Cameron via
2023-03-17 16:54 ` [RFC PATCH 1/4] hw/acpi: Make Aml and / or crs_range_set optional in build_crs Jonathan Cameron via
2023-03-17 16:54 ` [RFC PATCH 2/4] tests/acpi: Allow changes to DSDT.cxl/viot and SSDT.cxl/viot Jonathan Cameron via
2023-03-17 16:54 ` [RFC PATCH 3/4] hw/i386/acpi: Separate PXB related parts of DSDT into an SSDT table Jonathan Cameron via
2023-03-17 16:54 ` [RFC PATCH 4/4] tests/acpi: Updated DSDT and SSDT due to move of PXB info to SSDT Jonathan Cameron via
2023-04-06 10:25 ` [RFC PATCH 0/4] hw/i386: Factor out PXB parts of DSDT into an SSDT table Jonathan Cameron via
2023-04-07 7:37 ` Michael S. Tsirkin
2023-04-11 14:02 ` Igor Mammedov
2023-04-11 14:05 ` Michael S. Tsirkin [this message]
2023-04-11 14:25 ` 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=20230411100416-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=ani@anisinha.ca \
--cc=berrange@redhat.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=imammedo@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).