Re: Future of pci-mvebu

[Bjorn Helgaas <helgaas@kernel.org>]

On Tue, Jul 18, 2023 at 09:21:52PM +0200, Pali Rohár wrote:
> On Tuesday 18 July 2023 14:02:52 Bjorn Helgaas wrote:
> > On Tue, Jul 18, 2023 at 06:57:03PM +0200, Pali Rohár wrote:
> > > On Tuesday 18 July 2023 06:19:52 Bjorn Helgaas wrote:
> > > > On Tue, Jul 18, 2023 at 12:03:17AM +0200, Pali Rohár wrote:
> > > > > Hello, I have just one question. What do you want to do with pci-mvebu
> > > > > driver? It is already marked as broken for 3 kernel releases and I do
> > > > > not see any progress from anybody (and you rejected my fixes). How long
> > > > > do you want it to have marked as broken?
> > > > 
> > > > I don't think "depends on BROKEN" necessarily means that we plan to
> > > > remove the driver.  I think it just means that it's currently broken,
> > > > but we hope to fix it eventually.
> > > > 
> > > > I think the problem here is the regular vs chained interrupt handlers,
> > > > right?  Radu has been looking at that recently, too, so maybe we can
> > > > have another go at it.
> > > 
> > > I guess that this is the main issue as all other fixes and improvements
> > > are stalled. 
> > 
> > If these other things don't depend on this IRQ issue, maybe we could
> > still make progress on them?  Maybe post them again (rebasing to
> > v6.5-rc1 if necessary)?  Often I forget or miss things, so it doesn't
> > hurt to try again if you don't hear anything.
> 
> In past I (re)sent changes at least 3 times. And would not do it again.

Ouch, sorry.  How about links to them?

I browsed through the archives, and I did see a couple things that
apparently depended on the IRQ issue, but it wasn't obvious to me what
the others were.

Bjorn