Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: mvebu: Mark driver as BROKEN
Date: Tue, 8 Aug 2023 21:06:09 +0200	[thread overview]
Message-ID: <20230808190609.d7sbfklwlfo522lp@pali> (raw)
In-Reply-To: <ZNH8rM/EJQrEKsgo@shell.armlinux.org.uk>

On Tuesday 08 August 2023 09:28:28 Russell King (Oracle) wrote:
> On Tue, Aug 08, 2023 at 09:26:05AM +0200, Pali Rohár wrote:
> > On Friday 04 August 2023 12:35:13 Russell King (Oracle) wrote:
> > > Hi,
> > > 
> > > So it seems this patch got applied, but it wasn't Cc'd to
> > > linux-arm-kernel or anyone else, so those of us with platforms never
> > > had a chance to comment on it.
> > 
> > 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.
> 
> That's because I can't help - what I have *works*. I have *zero*
> issues with the PCI interfaces on Armada 388.

Perfect, apply your patch on your kernel setup and stop complaining
here. Nobody is interested for one Russel's user setup.

> > You should have come up and start solving issues. And not complaining
> > now.
> 
> How can one solve issues when they're probably hardware related and
> one doesn't experience them?
> 
> Sorry, but no.

Ok, if you do not want, that we have nothing to discuss here, and your
patch should be rejected.

> If you feel as strongly as you do, walk away.

What? You should go away and never return. Nobody is interested for one
nobody Russel user. Thanks.

And if you not agree with me, then go ahead and send a patch to remove
my maintainer line from this driver and explain to all people that you
are best one user on the world and that everybody should do what you
wrote.

  parent reply	other threads:[~2023-08-08 19:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 16:41 [PATCH] PCI: mvebu: Mark driver as BROKEN Pali Rohár
2023-01-15 22:02 ` Luís Mendes
2023-02-06 22:45 ` Pali Rohár
2023-02-09  9:02 ` Lorenzo Pieralisi
2023-08-04 11:35 ` Russell King (Oracle)
2023-08-04 13:46   ` Uwe Kleine-König
2023-08-04 17:00     ` Uwe Kleine-König
2023-08-08  7:27     ` Pali Rohár
2023-08-08  7:38       ` Uwe Kleine-König
2023-08-08  7:56         ` Pali Rohár
2023-08-04 14:54   ` Russell King (Oracle)
2023-08-08  7:27     ` Pali Rohár
2023-08-08  8:31       ` Russell King (Oracle)
2023-08-04 17:06   ` Bjorn Helgaas
2023-08-04 19:44     ` Russell King (Oracle)
2023-08-06 22:06       ` Luís Mendes
2023-08-08  7:31     ` Pali Rohár
2023-08-08  8:01       ` Uwe Kleine-König
2023-08-08 19:01         ` Pali Rohár
2023-08-08  8:32       ` Russell King (Oracle)
2023-08-08  7:26   ` Pali Rohár
2023-08-08  8:28     ` Russell King (Oracle)
2023-08-08  8:42       ` Russell King (Oracle)
2023-08-08 19:07         ` Pali Rohár
2023-08-08 19:06       ` Pali Rohár [this message]
2023-08-08 19:29         ` Russell King (Oracle)
2023-08-08 19:41         ` Bjorn Helgaas
2023-08-08 16:26     ` Bjorn Helgaas
2023-08-08 19:20       ` Pali Rohár
2023-08-08 19:54         ` Russell King (Oracle)

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=20230808190609.d7sbfklwlfo522lp@pali \
    --to=pali@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lpieralisi@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox