[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221108125613.GA463696@bhelgaas>
Date: Tue, 8 Nov 2022 06:56:13 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc: kishon@...nel.org, lpieralisi@...nel.org, bhelgaas@...gle.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
kw@...ux.com, robh@...nel.org, vidyas@...dia.com, vigneshr@...com
Subject: Re: [PATCH v4 0/5] PCI: endpoint: Rework the EPC to EPF notification
On Tue, Nov 08, 2022 at 05:44:40PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Nov 07, 2022 at 02:28:53PM -0600, Bjorn Helgaas wrote:
> > On Tue, Oct 25, 2022 at 08:20:56PM +0530, Manivannan Sadhasivam wrote:
> > > Hello,
> > >
> > > During the review of the patch that fixes DBI access in PCI EP, Rob
> > > suggested [1] using a fixed interface for passing the events from EPC to
> > > EPF instead of the in-kernel notifiers.
> >
> > > Manivannan Sadhasivam (5):
> > > PCI: dra7xx: Use threaded IRQ handler for "dra7xx-pcie-main" IRQ
> > > PCI: tegra194: Move dw_pcie_ep_linkup() to threaded IRQ handler
> > > PCI: endpoint: Use a separate lock for protecting epc->pci_epf list
> > > PCI: endpoint: Use callback mechanism for passing events from EPC to
> > > EPF
> > > PCI: endpoint: Use link_up() callback in place of LINK_UP notifier
> > >
> > > drivers/pci/controller/dwc/pci-dra7xx.c | 2 +-
> > > drivers/pci/controller/dwc/pcie-tegra194.c | 9 ++++-
> > > drivers/pci/endpoint/functions/pci-epf-test.c | 38 ++++++-------------
> > > drivers/pci/endpoint/pci-epc-core.c | 32 ++++++++++++----
> > > include/linux/pci-epc.h | 10 +----
> > > include/linux/pci-epf.h | 19 ++++++----
> > > 6 files changed, 59 insertions(+), 51 deletions(-)
> >
> > Doesn't apply cleanly on v6.1-rc1. Does it depend on something else?
>
> Yes, this patch:
> https://lore.kernel.org/linux-pci/20220825090101.20474-1-hayashi.kunihiko@socionext.com/
>
> Since this patch is already merged by Lorenzo, I based this series on top of
> that. If that's not required, I can send a new version without that patch.
I think it's fine as-is.
I tried applying it on both v6.1-rc1 and my current "next" branch.
Both failed because I haven't merged Lorenzo's branch into "next" yet.
As long as Lorenzo merges this on the correct branch, there's no
problem.
Mentioning the dependency or what the patch is based on in the cover
letter is the easiest way to make this smoother.
Bjorn
Powered by blists - more mailing lists