From: Bjorn Helgaas <helgaas@kernel.org>
To: Richard Zhu <hongxing.zhu@nxp.com>
Cc: l.stach@pengutronix.de, bhelgaas@google.com, broonie@kernel.org,
lorenzo.pieralisi@arm.com, jingoohan1@gmail.com,
festevam@gmail.com, stable@vger.kernel.org,
linux-pci@vger.kernel.org, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v5 3/6] PCI: imx6: PCI: imx6: Move imx6_pcie_clk_disable() earlier
Date: Wed, 5 Jan 2022 13:04:04 -0600 [thread overview]
Message-ID: <20220105190404.GA213307@bhelgaas> (raw)
In-Reply-To: <1641368602-20401-4-git-send-email-hongxing.zhu@nxp.com>
Remove repeated words from subject line.
On Wed, Jan 05, 2022 at 03:43:19PM +0800, Richard Zhu wrote:
> Just move the imx6_pcie_clk_disable() to an earlier place without function
> changes, since it wouldn't be only used in imx6_pcie_suspend_noirq() later.
next prev parent reply other threads:[~2022-01-05 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 7:43 [PATCH v5 0/6] PCI: imx6: refine codes and add compliance tests mode support Richard Zhu
2022-01-05 7:43 ` [PATCH v5 1/6] PCI: imx6: Encapsulate the clock enable into one standalone function Richard Zhu
2022-01-05 7:43 ` [PATCH v5 2/6] PCI: imx6: Add the error propagation from host_init Richard Zhu
2022-01-05 7:43 ` [PATCH v5 3/6] PCI: imx6: PCI: imx6: Move imx6_pcie_clk_disable() earlier Richard Zhu
2022-01-05 19:04 ` Bjorn Helgaas [this message]
2022-01-06 3:49 ` Hongxing Zhu
2022-01-05 7:43 ` [PATCH v5 4/6] PCI: dwc: Add dw_pcie_host_ops.host_exit() callback Richard Zhu
2022-01-05 7:43 ` [PATCH v5 5/6] PCI: imx6: Fix the regulator dump when link never came up Richard Zhu
2022-01-05 21:51 ` Fabio Estevam
2022-01-06 3:49 ` Hongxing Zhu
2022-01-06 10:38 ` Fabio Estevam
2022-01-05 7:43 ` [PATCH v5 6/6] PCI: imx6: Add the compliance tests mode support Richard Zhu
2022-01-05 10:15 ` [PATCH v5 0/6] PCI: imx6: refine codes and add " Greg KH
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=20220105190404.GA213307@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=hongxing.zhu@nxp.com \
--cc=jingoohan1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=stable@vger.kernel.org \
/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).