qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Barrat <fbarrat@linux.ibm.com>
To: clg@kaod.org, danielhb413@gmail.com, qemu-ppc@nongnu.org,
	qemu-devel@nongnu.org
Subject: [PATCH 1/4] ppc/pnv/pci: Cleanup PnvPHBPecState structure
Date: Fri, 27 Jan 2023 13:28:45 +0100	[thread overview]
Message-ID: <20230127122848.550083-2-fbarrat@linux.ibm.com> (raw)
In-Reply-To: <20230127122848.550083-1-fbarrat@linux.ibm.com>

Remove unused structure member 'system_memory'.

Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com>
---
 include/hw/pci-host/pnv_phb4.h | 2 --
 1 file changed, 2 deletions(-)

diff --git a/include/hw/pci-host/pnv_phb4.h b/include/hw/pci-host/pnv_phb4.h
index 1f3237c9d5..17aef08f91 100644
--- a/include/hw/pci-host/pnv_phb4.h
+++ b/include/hw/pci-host/pnv_phb4.h
@@ -173,8 +173,6 @@ struct PnvPhb4PecState {
     uint32_t index;
     uint32_t chip_id;
 
-    MemoryRegion *system_memory;
-
     /* Nest registers, excuding per-stack */
 #define PHB4_PEC_NEST_REGS_COUNT    0xf
     uint64_t nest_regs[PHB4_PEC_NEST_REGS_COUNT];
-- 
2.39.1



  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 ` Frederic Barrat [this message]
2023-01-27 16:15   ` [PATCH 1/4] ppc/pnv/pci: Cleanup PnvPHBPecState structure Cédric Le Goater
2023-01-27 12:28 ` [PATCH 2/4] ppc/pnv/pci: Remove duplicate definition of PNV_PHB5_DEVICE_ID Frederic Barrat
2023-01-27 16:16   ` 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-2-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).