From: Bjorn Helgaas <helgaas@kernel.org>
To: Ajay Agarwal <ajayagarwal@google.com>
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
"Johan Hovold" <johan+linaro@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Nikhil Devshatwar" <nikhilnd@google.com>,
"Manu Gautam" <manugautam@google.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Sajid Dalvi" <sdalvi@google.com>,
"William McVicker" <willmcvicker@google.com>,
linux-pci@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v4] PCI: dwc: Wait for link up only if link is started
Date: Tue, 25 Jul 2023 15:09:59 -0500 [thread overview]
Message-ID: <20230725200959.GA663593@bhelgaas> (raw)
In-Reply-To: <ZMAJCmfixoZmjPVI@google.com>
On Tue, Jul 25, 2023 at 11:10:26PM +0530, Ajay Agarwal wrote:
> Hi Jon,
> This issue has been reported on a QCOM platform as well. The patch will
> get reverted:
> https://lore.kernel.org/all/20230706082610.26584-1-johan+linaro@kernel.org/.
> Once it gets merged, I will upload a version of my patch where I would
> not fail the probe if the start_link() is defined and the link still
> does not come up.
>
> Johan, is your patch set to be picked in the next release?
I applied Johan's patch to for-linus, so it will appear in v6.5:
https://lore.kernel.org/linux-pci/20230725200515.GA663333@bhelgaas/
Bjorn
prev parent reply other threads:[~2023-07-25 20:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 9:34 [PATCH v4] PCI: dwc: Wait for link up only if link is started Ajay Agarwal
2023-04-19 19:29 ` William McVicker
2023-04-25 18:14 ` Ajay Agarwal
2023-04-25 19:07 ` Bjorn Helgaas
[not found] ` <CAHMEbQ-wuX1ky3v6JnAcPq752zbvoiZJ6AjXG863d7J3ATfqig@mail.gmail.com>
2023-05-12 17:00 ` William McVicker
2023-05-25 17:45 ` Ajay Agarwal
2023-05-26 8:46 ` Lorenzo Pieralisi
2023-07-25 15:30 ` Jon Hunter
2023-07-25 17:40 ` Ajay Agarwal
2023-07-25 20:09 ` Bjorn Helgaas [this message]
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=20230725200959.GA663593@bhelgaas \
--to=helgaas@kernel.org \
--cc=ajayagarwal@google.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=johan+linaro@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manugautam@google.com \
--cc=nikhilnd@google.com \
--cc=robh@kernel.org \
--cc=sdalvi@google.com \
--cc=willmcvicker@google.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).