From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Pali Rohár" <pali@kernel.org>,
"Krzysztof Wilczynski" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
linux-pci@vger.kernel.org, "Radu Rendec" <rrendec@redhat.com>
Subject: Re: Future of pci-mvebu
Date: Tue, 18 Jul 2023 17:20:52 +0530 [thread overview]
Message-ID: <20230718115052.GD4771@thinkpad> (raw)
In-Reply-To: <20230718111952.GA475778@bhelgaas>
On Tue, Jul 18, 2023 at 06:19:52AM -0500, Bjorn Helgaas wrote:
> [+cc Radu]
>
> 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.
>
We (Linaro and Redhat) had a discussion a while ago on this topic and I just got
pointed to Radu's series. So yes, we should instead work on that direction
instead of driver hacks which brings maintainers disagreement.
- Mani
> Bjorn
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-07-18 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 22:03 Future of pci-mvebu Pali Rohár
2023-07-18 9:16 ` Serge Semin
2023-07-18 11:19 ` Bjorn Helgaas
2023-07-18 11:50 ` Manivannan Sadhasivam [this message]
2023-07-18 11:54 ` Manivannan Sadhasivam
2023-07-18 16:57 ` Pali Rohár
2023-07-18 19:02 ` Bjorn Helgaas
2023-07-18 19:21 ` Pali Rohár
2023-07-18 19:28 ` Bjorn Helgaas
2023-07-18 19:40 ` Pali Rohár
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=20230718115052.GD4771@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=pali@kernel.org \
--cc=rrendec@redhat.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;
as well as URLs for NNTP newsgroup(s).