From: Fabio Estevam <festevam@gmail.com>
To: Hongxing Zhu <hongxing.zhu@nxp.com>
Cc: "l.stach@pengutronix.de" <l.stach@pengutronix.de>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"robh@kernel.org" <robh@kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI: imx6: Allow to probe when dw_pcie_wait_for_link() fails
Date: Wed, 3 Nov 2021 22:44:56 -0300 [thread overview]
Message-ID: <CAOMZO5CHOS9sczwa1ts4e0jaSjxa9CyGG8yCEJUjEj4BUf7Z2w@mail.gmail.com> (raw)
In-Reply-To: <AS8PR04MB8676C527C11B6E0BCB455E1B8C8D9@AS8PR04MB8676.eurprd04.prod.outlook.com>
Hi Richard,
On Wed, Nov 3, 2021 at 9:58 PM Hongxing Zhu <hongxing.zhu@nxp.com> wrote:
> [Richard Zhu] Hi Fabio:
> First of all, thanks for your help to care this bug.
> This dump is planned to be fixed in the #5 patch of
> '[v4,0/6] PCI: imx6: refine codes and add compliance tests mode support'
> "https://patchwork.kernel.org/project/linux-arm-kernel/cover/1635747478-25562-1-git-send-email-hongxing.zhu@nxp.com/"
Ok, great. Since this patch 5/6 is a bug fix, could you re-order this
series so that the bug fix is the first one in the series?
This makes it easier for the backport to stable.
Patch 1/6 is just a cleanup and could go further.
Thanks
next prev parent reply other threads:[~2021-11-04 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 0:02 [PATCH] PCI: imx6: Allow to probe when dw_pcie_wait_for_link() fails Fabio Estevam
2021-11-04 0:58 ` Hongxing Zhu
2021-11-04 1:44 ` Fabio Estevam [this message]
2021-11-05 8:18 ` Hongxing Zhu
2021-12-04 15:34 ` Fabio Estevam
2021-12-06 2:03 ` Hongxing Zhu
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=CAOMZO5CHOS9sczwa1ts4e0jaSjxa9CyGG8yCEJUjEj4BUf7Z2w@mail.gmail.com \
--to=festevam@gmail.com \
--cc=bhelgaas@google.com \
--cc=hongxing.zhu@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@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).