[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2510302003120.1185@angie.orcam.me.uk>
Date: Thu, 30 Oct 2025 20:10:17 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Bjorn Helgaas <helgaas@...nel.org>
cc: Thomas Bogendoerfer <tsbogend@...ha.franken.de>, 
    Thierry Reding <thierry.reding@...il.com>, 
    Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
    "Rafael J. Wysocki" <rafael@...nel.org>, x86@...nel.org, 
    linux-arm-kernel@...ts.infradead.org, linux-riscv@...ts.infradead.org, 
    linux-mips@...r.kernel.org, loongarch@...ts.linux.dev, 
    linuxppc-dev@...ts.ozlabs.org, linux-sh@...r.kernel.org, 
    linux-pci@...r.kernel.org, linux-acpi@...r.kernel.org, 
    linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/7] MIPS: PCI: Use contextual data instead of global
 variable
On Thu, 30 Oct 2025, Bjorn Helgaas wrote:
> It does complicate maintenance though.  I think all of mips ultimately
> uses register_pci_controller() and pcibios_scanbus().  Neither really
> contains anything mips-specific, so they duplicate a lot of the code
> in pci_host_probe().  Oh well, I guess that's part of the burden of
> supporting old platforms forever.
 FWIW new MIPS hardware continues being manufactured and if there is 
anything needed to clean up in generic MIPS/PCI platform code, then that 
can certainly be scheduled, subject to developers' resource availability.  
Individual MIPS platforms may vary of course, and with the solely legacy 
ones it will depend on the availability of hardware and engineers willing 
to maintain it.
  Maciej
Powered by blists - more mailing lists
 
