From: Frederic Barrat <fbarrat@linux.ibm.com>
To: clg@kaod.org, danielhb413@gmail.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Subject: [PATCH 2/4] ppc/pnv/pci: Remove duplicate definition of PNV_PHB5_DEVICE_ID
Date: Fri, 27 Jan 2023 13:28:46 +0100 [thread overview]
Message-ID: <20230127122848.550083-3-fbarrat@linux.ibm.com> (raw)
In-Reply-To: <20230127122848.550083-1-fbarrat@linux.ibm.com>
PNV_PHB5_DEVICE_ID is defined in two different headers. The definition
in hw/pci-host/pnv_phb4.h was left out in a previous rework.
Remaining definition is in hw/pci-host/pnv_phb.h.
Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>
---
include/hw/pci-host/pnv_phb4.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/hw/pci-host/pnv_phb4.h b/include/hw/pci-host/pnv_phb4.h
index 17aef08f91..761525686e 100644
--- a/include/hw/pci-host/pnv_phb4.h
+++ b/include/hw/pci-host/pnv_phb4.h
@@ -215,7 +215,6 @@ struct PnvPhb4PecClass {
OBJECT_CHECK(PnvPhb4, (obj), TYPE_PNV_PHB5)
#define PNV_PHB5_VERSION 0x000000a500000001ull
-#define PNV_PHB5_DEVICE_ID 0x0652
#define TYPE_PNV_PHB5_PEC "pnv-phb5-pec"
#define PNV_PHB5_PEC(obj) \
--
2.39.1
next prev parent reply other threads:[~2023-01-27 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 12:28 [PATCH 0/4] PCI-related cleanup for ppc/powernv Frederic Barrat
2023-01-27 12:28 ` [PATCH 1/4] ppc/pnv/pci: Cleanup PnvPHBPecState structure Frederic Barrat
2023-01-27 16:15 ` Cédric Le Goater
2023-01-27 12:28 ` Frederic Barrat [this message]
2023-01-27 16:16 ` [PATCH 2/4] ppc/pnv/pci: Remove duplicate definition of PNV_PHB5_DEVICE_ID Cédric Le Goater
2023-01-27 12:28 ` [PATCH 3/4] ppc/pnv/pci: Update PHB5 version register Frederic Barrat
2023-01-27 16:18 ` Cédric Le Goater
2023-01-27 12:28 ` [PATCH 4/4] ppc/pnv/pci: Fix PHB xscom registers memory region name Frederic Barrat
2023-01-27 16:19 ` Cédric Le Goater
2023-01-28 23:32 ` [PATCH 0/4] PCI-related cleanup for ppc/powernv Daniel Henrique Barboza
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=20230127122848.550083-3-fbarrat@linux.ibm.com \
--to=fbarrat@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).