From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: "Francesco Dolcini" <francesco.dolcini@toradex.com>,
"Richard Zhu" <hongxing.zhu@nxp.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Bjorn Helgaas" <helgaas@kernel.org>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
pali@kernel.org
Subject: Re: [PATCH v3] PCI: imx6: Fix PERST# start-up sequence
Date: Mon, 9 May 2022 16:09:19 +0200 [thread overview]
Message-ID: <20220509140919.GA7159@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220411165031.GA28780@lpieralisi>
Hello Lorenzo,
On Mon, Apr 11, 2022 at 05:50:41PM +0100, Lorenzo Pieralisi wrote:
> [CC'ed Pali, who is working on PERST consolidation]
>
> On Mon, Apr 04, 2022 at 10:15:09AM +0200, Francesco Dolcini wrote:
> > Failure to do so could prevent PCIe devices to be working correctly,
> > and this was experienced with real devices.
Just a gentle ping, any concern on the patch?
Francesco
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-09 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:15 [PATCH v3] PCI: imx6: Fix PERST# start-up sequence Francesco Dolcini
2022-04-11 16:00 ` Lucas Stach
2022-04-11 16:50 ` Lorenzo Pieralisi
2022-05-09 14:09 ` Francesco Dolcini [this message]
2022-05-10 17:49 ` Lorenzo Pieralisi
2022-05-11 7:13 ` Francesco Dolcini
2022-05-11 9:32 ` Pali Rohár
2022-05-11 12:51 ` Lorenzo Pieralisi
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=20220509140919.GA7159@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=festevam@gmail.com \
--cc=helgaas@kernel.org \
--cc=hongxing.zhu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kw@linux.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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