From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Cc: npiggin@gmail.com, danielhb413@gmail.com, clg@kaod.org
Subject: Re: [PATCH 1/3] ppc/spapr: remove deprecated machine pseries-3.0
Date: Thu, 8 May 2025 09:18:57 +0200 [thread overview]
Message-ID: <15908e2f-544d-4f14-ba9a-8058bfb7d46b@linaro.org> (raw)
In-Reply-To: <20250507052048.90559-2-harshpb@linux.ibm.com>
Hi Harsh,
On 7/5/25 07:20, Harsh Prateek Bora wrote:
> pseries-3.0 had been deprecated and due for removal now as per policy.
> Also remove legacy irq support which existed for pre pseries-3.1 machines.
"Also" suggests this patch could be split in 2 distinct changes,
easier to review / bisect / backport.
>
> Suggested-by: Cédric Le Goater <clg@kaod.org>
> Signed-off-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
> ---
> include/hw/ppc/spapr.h | 1 -
> include/hw/ppc/spapr_irq.h | 1 -
> hw/ppc/spapr.c | 27 +--------------------------
> hw/ppc/spapr_events.c | 8 --------
> hw/ppc/spapr_irq.c | 16 +---------------
> hw/ppc/spapr_pci.c | 32 ++++----------------------------
> hw/ppc/spapr_vio.c | 9 ---------
> 7 files changed, 6 insertions(+), 88 deletions(-)
next prev parent reply other threads:[~2025-05-08 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 5:20 [PATCH 0/3] ppc/spapr: remove deprecated machines till pseries-4.0 Harsh Prateek Bora
2025-05-07 5:20 ` [PATCH 1/3] ppc/spapr: remove deprecated machine pseries-3.0 Harsh Prateek Bora
2025-05-08 7:18 ` Philippe Mathieu-Daudé [this message]
2025-05-07 5:20 ` [PATCH 2/3] ppc/spapr: remove deprecated machine pseries-3.1 Harsh Prateek Bora
2025-05-08 7:19 ` Philippe Mathieu-Daudé
2025-05-07 5:20 ` [PATCH 3/3] ppc/spapr: remove deprecated machine pseries-4.0 Harsh Prateek Bora
2025-05-08 7:19 ` Philippe Mathieu-Daudé
2025-10-09 5:16 ` Harsh Prateek Bora
2025-05-07 5:40 ` [PATCH 0/3] ppc/spapr: remove deprecated machines till pseries-4.0 Cédric Le Goater
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=15908e2f-544d-4f14-ba9a-8058bfb7d46b@linaro.org \
--to=philmd@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.