Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org
Subject: [PATCH] PCI: mvebu: Mark driver as BROKEN
Date: Sat, 14 Jan 2023 17:41:25 +0100	[thread overview]
Message-ID: <20230114164125.1298-1-pali@kernel.org> (raw)

People are reporting that pci-mvebu.c driver does not work with recent
mainline kernel. There are more bugs which prevents its for daily usage.
So lets mark it as broken for now, until somebody would be able to fix it
in mainline kernel.

Signed-off-by: Pali Rohár <pali@kernel.org>

---
Bjorn: I would really appreciate if you take this change and send it in
pull request for v6.2 release. There is no reason to wait more longer.


I'm periodically receiving emails that driver does not work correctly
anymore, PCIe cards are not detected or that they crashes during boot.

Some of the issues are handled in patches which are waiting on the list for
a long time and nobody cares for them. Some others needs investigation.

I'm really tired in replying to those user emails as I cannot do more in
this area. I have asked more people for help but either there were only
promises without any action for more than year or simple no direction how
to move forward or what to do with it.

So mark this driver as broken. Users would see the real current state
and hopefully will stop reporting me old or new bugs.
---
 drivers/pci/controller/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/pci/controller/Kconfig b/drivers/pci/controller/Kconfig
index 1569d9a3ada0..b4a4d84a358b 100644
--- a/drivers/pci/controller/Kconfig
+++ b/drivers/pci/controller/Kconfig
@@ -9,6 +9,7 @@ config PCI_MVEBU
 	depends on MVEBU_MBUS
 	depends on ARM
 	depends on OF
+	depends on BROKEN
 	select PCI_BRIDGE_EMUL
 	help
 	 Add support for Marvell EBU PCIe controller. This PCIe controller
-- 
2.20.1


             reply	other threads:[~2023-01-14 16:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 16:41 Pali Rohár [this message]
2023-01-15 22:02 ` [PATCH] PCI: mvebu: Mark driver as BROKEN 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
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=20230114164125.1298-1-pali@kernel.org \
    --to=pali@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    /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