From: Hongxing Zhu <hongxing.zhu@nxp.com>
To: Fabio Estevam <festevam@gmail.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: Fri, 5 Nov 2021 08:18:31 +0000 [thread overview]
Message-ID: <AS8PR04MB86766C25BF33050C342DE47E8C8E9@AS8PR04MB8676.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAOMZO5CHOS9sczwa1ts4e0jaSjxa9CyGG8yCEJUjEj4BUf7Z2w@mail.gmail.com>
> -----Original Message-----
> From: Fabio Estevam <festevam@gmail.com>
> Sent: Thursday, November 4, 2021 9:45 AM
> To: Hongxing Zhu <hongxing.zhu@nxp.com>
> Cc: l.stach@pengutronix.de; lorenzo.pieralisi@arm.com;
> robh@kernel.org; bhelgaas@google.com; linux-pci@vger.kernel.org
> Subject: Re: [PATCH] PCI: imx6: Allow to probe when
> dw_pcie_wait_for_link() fails
>
> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fp
> atchwork.kernel.org%2Fproject%2Flinux-arm-kernel%2Fcover%2F163574
> 7478-25562-1-git-send-email-hongxing.zhu%40nxp.com%2F&data=
> 04%7C01%7Chongxing.zhu%40nxp.com%7Ca96f456b0a004a4da69008d9
> 9f34bb8b%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C6377
> 15871101762967%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM
> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&
> sdata=bZInvFrlHI8VmWiIS2oxfraSCFAEhWmPG%2BtHLwNHD7A%3D&am
> p;reserved=0"
>
> 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.
[Richard Zhu] Hi Fabio: The #5 patch relies on the changes of #2-4 patches.
And the #1 patch make the changes of #2 easier.
It's better to keep the sequence of the v4 series.
BR
Richard
>
> Thanks
next prev parent reply other threads:[~2021-11-05 8:18 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
2021-11-05 8:18 ` Hongxing Zhu [this message]
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=AS8PR04MB86766C25BF33050C342DE47E8C8E9@AS8PR04MB8676.eurprd04.prod.outlook.com \
--to=hongxing.zhu@nxp.com \
--cc=bhelgaas@google.com \
--cc=festevam@gmail.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).