From: Johan Hovold <johan@kernel.org>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Stanimir Varbanov" <svarbanov@mm-sol.com>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] PCI: qcom: Fix probe error paths
Date: Wed, 27 Apr 2022 09:42:39 +0200 [thread overview]
Message-ID: <Ymjz76YFLU28CUzn@hovoldconsulting.com> (raw)
In-Reply-To: <20220401133854.10421-1-johan+linaro@kernel.org>
On Fri, Apr 01, 2022 at 03:38:52PM +0200, Johan Hovold wrote:
> This series fixes a few problems in the probe error handling which could
> cause trouble, for example, on probe deferral.
> Johan Hovold (2):
> PCI: qcom: Fix runtime PM imbalance on probe errors
> PCI: qcom: Fix unbalanced PHY init on probe errors
>
> drivers/pci/controller/dwc/pcie-qcom.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
Any comments to this series? Does it need a Qualcomm maintainer ack to
be merged? Bjorn?
Johan
next prev parent reply other threads:[~2022-04-27 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 13:38 [PATCH v2 0/2] PCI: qcom: Fix probe error paths Johan Hovold
2022-04-01 13:38 ` [PATCH v2 1/2] PCI: qcom: Fix runtime PM imbalance on probe errors Johan Hovold
2022-04-27 7:54 ` Manivannan Sadhasivam
2022-04-01 13:38 ` [PATCH v2 2/2] PCI: qcom: Fix unbalanced PHY init " Johan Hovold
2022-04-27 7:55 ` Manivannan Sadhasivam
2022-04-27 7:42 ` Johan Hovold [this message]
2022-04-27 7:56 ` [PATCH v2 0/2] PCI: qcom: Fix probe error paths Stanimir Varbanov
2022-04-27 9:09 ` 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=Ymjz76YFLU28CUzn@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=svarbanov@mm-sol.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;
as well as URLs for NNTP newsgroup(s).