All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: milesg@linux.ibm.com,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Laurent Vivier" <laurent@vivier.eu>,
	"Chinmay Rath" <rathc@linux.ibm.com>
Subject: Re: [PATCH 3/9] ppc/ppc405: Remove CPU
Date: Tue, 5 May 2026 09:22:43 +0100	[thread overview]
Message-ID: <afmo00Lm0ajJ6I9b@redhat.com> (raw)
In-Reply-To: <1bf864b8-0dcf-45d6-a2fc-fc34b1bafe97@redhat.com>

On Mon, May 04, 2026 at 11:48:57AM +0200, Cédric Le Goater wrote:
> Hello Glenn,
> 
> 
> On 4/30/26 17:43, Miles Glenn wrote:
> > On Thu, 2026-04-30 at 17:15 +0200, Philippe Mathieu-Daudé wrote:
> > > Hi Harsh,
> > > 
> > > On 30/4/26 08:54, Harsh Prateek Bora wrote:
> > > > Adding Glenn (since PPE42 seems to make use of CONFIG_PPC405)
> > > > 
> > > > Glenn,
> > > > Please take a look and let us know your thoughts.
> > > 
> > > Glenn can have a look, but I think we are good to remove them now,
> > > they have been deprecated for more than 1 year, enough time for
> > > any reaction ;) Otherwise that'd defeat the point of deprecating
> > > and the pain for us to schedule and wait for months.
> > 
> > Philippe,
> > 
> > Sorry, I thought it had been made clear back in August of last year
> > that we would need the PPC405 CPU to hang around.  The topic was
> > brought up by Cedric when I added support for the PPE42 processor.  Is
> > there some formal process I need to go through to have it removed from
> > the deprecated list?
> 
> I don't know of any un-deprecation process. I suggest sending a patch
> to revert commit 52f0b59ec6b7 ("hw/ppc: Deprecate 405 CPUs"). The commit
> log should mention the PPE42 processor which is a stripped down version
> of the IBM PowerPC 405 processor.

Yes, that's exactly the process - just remove the text from deprecated.rst
and warning messages printed by the code (if any)

Daniel



  parent reply	other threads:[~2026-05-05  8:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 14:17 [PATCH 0/9] ppc: Remove 405 CPU family Cédric Le Goater
2025-01-10 14:17 ` [PATCH 1/9] ppc/ppc405: Remove tests Cédric Le Goater
2025-01-10 16:04   ` Philippe Mathieu-Daudé
2025-01-10 14:17 ` [PATCH 2/9] ppc/ppc405: Remove boards Cédric Le Goater
2025-01-10 16:05   ` Philippe Mathieu-Daudé
2025-01-10 14:17 ` [PATCH 3/9] ppc/ppc405: Remove CPU Cédric Le Goater
2025-01-10 16:15   ` Philippe Mathieu-Daudé
2025-01-10 16:25     ` Richard Henderson
2025-01-14  7:11       ` Nicholas Piggin
2025-01-14  7:47         ` Cédric Le Goater
2026-04-30  5:30           ` Philippe Mathieu-Daudé
2026-04-30  6:54             ` Harsh Prateek Bora
2026-04-30 15:15               ` Philippe Mathieu-Daudé
2026-04-30 15:43                 ` Miles Glenn
2026-05-04  9:48                   ` Cédric Le Goater
2026-05-04 12:32                     ` Philippe Mathieu-Daudé
2026-05-04 14:59                       ` Miles Glenn
2026-05-04 17:32                         ` Miles Glenn
2026-05-05  8:22                     ` Daniel P. Berrangé [this message]
2026-04-30 15:35               ` Miles Glenn
2025-01-16 10:57         ` Daniel Henrique Barboza
2025-01-10 14:17 ` [PATCH 4/9] ppc/ppc405: Remove storage control (SLER) SPR Cédric Le Goater
2025-01-10 14:17 ` [PATCH 5/9] ppc/ppc405: Remove 40x exception model Cédric Le Goater
2025-01-10 14:17 ` [PATCH 6/9] ppc/ppc405: Remove timer support Cédric Le Goater
2025-01-10 14:17 ` [PATCH 7/9] ppc/ppc405: Remove cache handling instructions Cédric Le Goater
2025-01-10 16:09   ` Philippe Mathieu-Daudé
2025-01-10 16:15     ` Cédric Le Goater
2025-01-10 14:17 ` [PATCH 8/9] ppc/ppc405: Remove TLB instructions Cédric Le Goater
2025-01-10 14:18 ` [PATCH 9/9] ppc/ppc405: Remove POWERPC_MMU_SOFT_4xx MMU model 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=afmo00Lm0ajJ6I9b@redhat.com \
    --to=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=danielhb413@gmail.com \
    --cc=harshpb@linux.ibm.com \
    --cc=laurent@vivier.eu \
    --cc=milesg@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rathc@linux.ibm.com \
    --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 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.