From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kishon@kernel.org, lpieralisi@kernel.org, bhelgaas@google.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kw@linux.com, robh@kernel.org, vidyas@nvidia.com,
vigneshr@ti.com
Subject: Re: [PATCH v4 0/5] PCI: endpoint: Rework the EPC to EPF notification
Date: Mon, 7 Nov 2022 14:28:53 -0600 [thread overview]
Message-ID: <20221107202853.GA416802@bhelgaas> (raw)
In-Reply-To: <20221025145101.116393-1-manivannan.sadhasivam@linaro.org>
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?
next prev parent reply other threads:[~2022-11-07 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 14:50 [PATCH v4 0/5] PCI: endpoint: Rework the EPC to EPF notification Manivannan Sadhasivam
2022-10-25 14:50 ` [PATCH v4 1/5] PCI: dra7xx: Use threaded IRQ handler for "dra7xx-pcie-main" IRQ Manivannan Sadhasivam
2022-10-25 14:50 ` [PATCH v4 2/5] PCI: tegra194: Move dw_pcie_ep_linkup() to threaded IRQ handler Manivannan Sadhasivam
2022-11-14 11:06 ` Manivannan Sadhasivam
2022-11-14 11:08 ` Manivannan Sadhasivam
2022-11-22 13:49 ` Manivannan Sadhasivam
2022-12-05 6:49 ` Manivannan Sadhasivam
2022-10-25 14:50 ` [PATCH v4 3/5] PCI: endpoint: Use a separate lock for protecting epc->pci_epf list Manivannan Sadhasivam
2022-10-25 14:51 ` [PATCH v4 4/5] PCI: endpoint: Use callback mechanism for passing events from EPC to EPF Manivannan Sadhasivam
2022-11-08 5:52 ` Kishon Vijay Abraham I
2022-10-25 14:51 ` [PATCH v4 5/5] PCI: endpoint: Use link_up() callback in place of LINK_UP notifier Manivannan Sadhasivam
2022-11-08 5:55 ` Kishon Vijay Abraham I
2022-11-05 6:53 ` [PATCH v4 0/5] PCI: endpoint: Rework the EPC to EPF notification Manivannan Sadhasivam
2022-11-07 20:28 ` Bjorn Helgaas [this message]
2022-11-08 12:14 ` Manivannan Sadhasivam
2022-11-08 12:56 ` Bjorn Helgaas
2022-11-14 7:33 ` Manivannan Sadhasivam
2022-11-14 10:05 ` Lorenzo Pieralisi
2022-11-14 10:20 ` 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=20221107202853.GA416802@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=vidyas@nvidia.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.