Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Jan Palus <jpalus@fastmail.com>,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [Bug 220479] New: [regression 6.16] mvebu: no pci devices detected on turris omnia
Date: Wed, 3 Sep 2025 09:35:58 +0200	[thread overview]
Message-ID: <20250903073558.6v2d7q6n6hm2vv3a@pali> (raw)
In-Reply-To: <CAL_Jsq+cytAQAtSB7VjR8oKrXJJSSrOouKQZYQAWNvu+tStTnA@mail.gmail.com>

On Tuesday 02 September 2025 20:35:14 Rob Herring wrote:
> On Tue, Sep 2, 2025 at 3:32 PM Pali Rohár <pali@kernel.org> wrote:
> >
> > These issues have been discussed more times for last 3 years.
> > Tested changes which are fixing real bugs and are improving the
> > pci-mvebu.c driver from people listed as M: in MAINTAINERS are being
> > rejected or silently ignored. And untested changes which are not going
> > to fix any bug are being accepted and causing new regressions. People
> > then reporting bug reports to M: people who cannot do anything with it.
> > The only advice which they can get is to not use mainline kernel.
> > This pci-mvebu.c driver in mainline kernel is broken and nobody wanted
> > to do anything with this situation for last 3 years, I was pointing for
> > it more times. Due to this I'm ignoring bug reports for pci-mvebu.c
> > driver for mainline kernel.
> 
> This makes no sense. Mainline is broken, but yet there's a regression
> in mainline breaking the driver. The pci-mvebu.c maintainers have the
> ability to test patches, but refuse to test any submitted patches
> other than their own. I guess the only solution here is just remove
> the driver...
> 
> Rob

This is not the way how to get patches being tested. Ignoring other
people and taking untested patches because you did not wanted to
communicate with maintainers. I have no reason to test other patches if
my own are being ignored. This is fair. In past I spent lot of time on
addressing issues in this driver, preparing fixes for real bugs and
whole time was wasted. And if you expected that it would work in that,
then go ahead and do it, remove the driver.


  reply	other threads:[~2025-09-03  8:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-220479-41252@https.bugzilla.kernel.org/>
2025-08-20 18:46 ` [Bug 220479] New: [regression 6.16] mvebu: no pci devices detected on turris omnia Bjorn Helgaas
2025-08-20 19:08   ` Jan Palus
2025-08-20 19:30     ` Bjorn Helgaas
2025-08-20 19:51       ` Jan Palus
2025-08-21  0:45   ` Jan Palus
2025-09-02  9:09     ` Klaus Kudielka
2025-09-02 10:33       ` Klaus Kudielka
2025-09-02 20:32   ` Pali Rohár
2025-09-03  1:35     ` Rob Herring
2025-09-03  7:35       ` Pali Rohár [this message]
2025-09-03  7:50         ` Manivannan Sadhasivam

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=20250903073558.6v2d7q6n6hm2vv3a@pali \
    --to=pali@kernel.org \
    --cc=helgaas@kernel.org \
    --cc=jpalus@fastmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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