[PATCH] PCI: mvebu: Mark driver as BROKEN

[Russell King (Oracle)]

On Tue, Aug 08, 2023 at 09:20:26PM +0200, Pali Rohár wrote:
> There area other options which can be done now, if there are only people
> like Russel who are complaining but refusing to do absolutely nothing.

Fucking hell, here we go with the accusations again.

And you can't even be bothered to spell my name correctly.

Let's start over at your first accusation in this thread, because this
says everything about what the problem here is:

"You have received more changes and fixes for last 2 years for these
issues and you have done **nothing**. You even not said anything.
So you are the last one who can complain here.

And I'm stopped communicating with people who do not want to communicate
with me. This is pretty normal situation and you should have think about
it. No?"

Let's go through my points one by one, maybe you'll then understand,
because right now you seem to be totally immune to any appreciation
of anyone's situation other than your own.

1. pci-mvebu works 100% fine for me.

2. I do not see any problems with the hardware I have. If I have no
   problems, then by definition it works fine. How can I test - for
   example, failure to bring up the PCIe link (which I believe some
   of your patches were trying to address) when I HAVE NO PROBLEM WITH
   THE PCIe LINK NOT COMING UP? FFS, take a moment to think about that.

3. I have not asked you to work on it.

4. You do not have the right to demand that I do anything with it.

5. You decided to pick up some patches that I had in my tree and
   merge them into the kernel.

6. You objected when I rebased my branches on top of what you had
   merged (which were modified versions of my patches). I wanted to
   keep my changes intact.

   (Again, you have no damn right in this whole damned world to
   complain about what I do in my own git tree.)

7. You decided on your own back to mark the driver BROKEN - and you
   did that in such a way to *ensure* that no one who would have
   been using it would notice until after the patch was merged. That
   is underhand tactics. You effectively admit to that in my above
   quotation, which effectively states that you _actively_ decided
   to exclude me from that because I didn't interact with you.

> For example mark driver as experimental (there is some Kconfig symbol
> for it). Or add a new menuconfig selectable symbol which appropriately
> warn all distributions about problems and would be dependency for mvebu.
> (if you do not like broken symbol).

So distributions end up crippling systems that they've stated that they
support? That is the side effect of your patch?

I welcome your resignation as maintainer of this driver - and at this
point I think that is the best course of action given everything that
has happened. Yes - you have now driven me to actively seek your
resignation.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!