From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, ani@anisinha.ca, pbonzini@redhat.com,
richard.henderson@linaro.org, mark.cave-ayland@ilande.co.uk,
peter.maydell@linaro.org, andrew.smirnov@gmail.com,
paulburton@kernel.org, aleksandar.rikalo@syrmia.com,
danielhb413@gmail.com, clg@kaod.org, david@gibson.dropbear.id.au,
groug@kaod.org, qemu-arm@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v2 for-8.0 0/2] pci: drop redundant PCIDeviceClass::is_bridge field
Date: Wed, 14 Dec 2022 06:39:43 -0500 [thread overview]
Message-ID: <20221214063852-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221214100943.7f64a34b@imammedo.users.ipa.redhat.com>
On Wed, Dec 14, 2022 at 10:09:43AM +0100, Igor Mammedov wrote:
> On Tue, 29 Nov 2022 11:13:39 +0100
> Igor Mammedov <imammedo@redhat.com> wrote:
>
> > Changelog:
> > - keep comment reminding that there was a bridge, so it would be easy to find
> > removed code if someone wishes to bring it back
> > - s/IS_PCI_BRIDGE/is_bridge/ in one instance where local is_bridge already exists
>
> Michael,
>
> can you merge this via PCI tree?
Yes it's tagged. Busy with the linux pull req, qemu pull req next.
Thanks for the reminder!
> >
> > Igor Mammedov (2):
> > remove DEC 21154 PCI bridge
> > pci: drop redundant PCIDeviceClass::is_bridge field
> >
> > hw/pci-bridge/dec.h | 9 --
> > include/hw/pci/pci.h | 11 +-
> > include/hw/pci/pci_bridge.h | 1 +
> > include/hw/pci/pci_ids.h | 1 -
> > hw/acpi/pcihp.c | 3 +-
> > hw/i386/acpi-build.c | 5 +-
> > hw/pci-bridge/cxl_downstream.c | 1 -
> > hw/pci-bridge/cxl_upstream.c | 1 -
> > hw/pci-bridge/dec.c | 164 -----------------------------
> > hw/pci-bridge/i82801b11.c | 1 -
> > hw/pci-bridge/meson.build | 2 -
> > hw/pci-bridge/pci_bridge_dev.c | 1 -
> > hw/pci-bridge/pcie_pci_bridge.c | 1 -
> > hw/pci-bridge/pcie_root_port.c | 1 -
> > hw/pci-bridge/simba.c | 1 -
> > hw/pci-bridge/xio3130_downstream.c | 1 -
> > hw/pci-bridge/xio3130_upstream.c | 1 -
> > hw/pci-host/designware.c | 1 -
> > hw/pci-host/uninorth.c | 9 +-
> > hw/pci-host/xilinx-pcie.c | 1 -
> > hw/pci/pci.c | 20 ++--
> > hw/ppc/spapr_pci.c | 15 +--
> > 22 files changed, 23 insertions(+), 228 deletions(-)
> > delete mode 100644 hw/pci-bridge/dec.h
> > delete mode 100644 hw/pci-bridge/dec.c
> >
prev parent reply other threads:[~2022-12-14 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 10:13 [PATCH v2 for-8.0 0/2] pci: drop redundant PCIDeviceClass::is_bridge field Igor Mammedov
2022-11-29 10:13 ` [PATCH v2 for-8.0 1/2] remove DEC 21154 PCI bridge Igor Mammedov
2022-11-29 10:13 ` [PATCH v2 for-8.0 2/2] pci: drop redundant PCIDeviceClass::is_bridge field Igor Mammedov
2022-11-30 11:20 ` Greg Kurz
2022-12-14 9:09 ` [PATCH v2 for-8.0 0/2] " Igor Mammedov
2022-12-14 11:39 ` Michael S. Tsirkin [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=20221214063852-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=andrew.smirnov@gmail.com \
--cc=ani@anisinha.ca \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=paulburton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).