From: Frank Li <Frank.li@nxp.com>
To: manivannan.sadhasivam@linaro.org
Cc: imx@lists.linux.dev, kw@linux.com, linux-pci@vger.kernel.org,
lpieralisi@kernel.org, linux-kernel@vger.kernel.org,
minghuan.Lian@nxp.com, mingkai.hu@nxp.com, roy.zang@nxp.com,
bhelgaas@google.com, linuxppc-dev@lists.ozlabs.org,
robh@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] PCI: layerscape: Add suspend/resume support for ls1043 and ls1021
Date: Fri, 27 Oct 2023 12:27:00 -0400 [thread overview]
Message-ID: <ZTvk1Mo/cg0CKKJ3@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20231017193145.3198380-1-Frank.Li@nxp.com>
On Tue, Oct 17, 2023 at 03:31:41PM -0400, Frank Li wrote:
> Add suspend/resume support for ls1043 and ls1021.
> Change log see each patch
>
> Frank Li (4):
> PCI: layerscape: Add function pointer for exit_from_l2()
> PCI: layerscape: Add suspend/resume for ls1021a
> PCI: layerscape: Rename pf_* as pf_lut_*
> PCI: layerscape: Add suspend/resume for ls1043a
>
@mani:
Do you have any additional comments for these?
Frank
> drivers/pci/controller/dwc/pci-layerscape.c | 217 ++++++++++++++++++--
> 1 file changed, 196 insertions(+), 21 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-10-27 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 19:31 [PATCH v3 0/4] PCI: layerscape: Add suspend/resume support for ls1043 and ls1021 Frank Li
2023-10-17 19:31 ` [PATCH v3 1/4] PCI: layerscape: Add function pointer for exit_from_l2() Frank Li
2023-11-02 16:58 ` Manivannan Sadhasivam
2023-11-02 18:01 ` Frank Li
2023-10-17 19:31 ` [PATCH v3 2/4] PCI: layerscape: Add suspend/resume for ls1021a Frank Li
2023-11-02 17:28 ` Manivannan Sadhasivam
2023-11-02 18:14 ` Frank Li
2023-10-17 19:31 ` [PATCH v3 3/4] PCI: layerscape: Rename pf_* as pf_lut_* Frank Li
2023-11-02 17:33 ` Manivannan Sadhasivam
2023-11-02 18:21 ` Frank Li
2023-10-17 19:31 ` [PATCH v3 4/4] PCI: layerscape: Add suspend/resume for ls1043a Frank Li
2023-11-02 17:39 ` Manivannan Sadhasivam
2023-11-02 18:29 ` Frank Li
2023-10-27 16:27 ` Frank Li [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=ZTvk1Mo/cg0CKKJ3@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=bhelgaas@google.com \
--cc=imx@lists.linux.dev \
--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=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=minghuan.Lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=robh@kernel.org \
--cc=roy.zang@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