From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: frank.li@nxp.com, Frank Li <Frank.Li@nxp.com>
Cc: robh@kernel.org, imx@lists.linux.dev, xiaowei.bao@nxp.com,
kw@linux.com, linux-pci@vger.kernel.org,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
mani@kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org, minghuan.Lian@nxp.com,
markus.elfring@web.de, mingkai.hu@nxp.com, roy.zang@nxp.com,
bhelgaas@google.com, linuxppc-dev@lists.ozlabs.org,
Zhiqiang.Hou@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] PCI: layerscape: Add support for Link down notification
Date: Thu, 24 Aug 2023 10:14:38 +0200 [thread overview]
Message-ID: <169286486358.59705.3375218028619595727.b4-ty@kernel.org> (raw)
In-Reply-To: <20230720135834.1977616-1-Frank.Li@nxp.com>
On Thu, 20 Jul 2023 09:58:33 -0400, Frank Li wrote:
> Add support to pass Link down notification to Endpoint function driver
> so that the LINK_DOWN event can be processed by the function.
>
>
Applied to controller/layerscape, thanks!
[1/2] PCI: layerscape: Add support for Link down notification
https://git.kernel.org/pci/pci/c/d28c0d84ca40
[2/2] PCI: layerscape: Add the workaround for lost link capabilities during reset.
https://git.kernel.org/pci/pci/c/17cf8661ee0f
Thanks,
Lorenzo
prev parent reply other threads:[~2023-08-24 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 13:58 [PATCH v4 1/2] PCI: layerscape: Add support for Link down notification Frank Li
2023-07-20 13:58 ` [PATCH v4 2/2] PCI: layerscape: Add the workaround for lost link capabilities during reset Frank Li
2023-07-31 15:06 ` [PATCH v4 1/2] PCI: layerscape: Add support for Link down notification Frank Li
2023-08-16 15:53 ` Frank Li
2023-08-23 15:54 ` Frank Li
2023-08-23 16:11 ` Lorenzo Pieralisi
2023-08-24 8:14 ` Lorenzo Pieralisi [this message]
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=169286486358.59705.3375218028619595727.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bhelgaas@google.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mani@kernel.org \
--cc=markus.elfring@web.de \
--cc=minghuan.Lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh@kernel.org \
--cc=roy.zang@nxp.com \
--cc=xiaowei.bao@nxp.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