From: Kishon Vijay Abraham I <kishon@ti.com>
To: Sasha Levin <sashal@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>,
Vivek Gautam <vivek.gautam@codeaurora.org>,
Evan Green <evgreen@chromium.org>,
Niklas Cassel <niklas.cassel@linaro.org>
Subject: Re: [PATCH] phy: qcom-qmp: Correct ready status, again
Date: Wed, 21 Aug 2019 05:53:47 +0530 [thread overview]
Message-ID: <57556d09-e2db-dc00-45a9-cbb57da02319@ti.com> (raw)
In-Reply-To: <20190806155040.0B54520C01@mail.kernel.org>
Hi Sasha,
On 06/08/19 9:20 PM, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: 885bd765963b phy: qcom-qmp: Correct READY_STATUS poll break condition.
>
> The bot has tested the following trees: v5.2.6.
>
> v5.2.6: Failed to apply! Possible dependencies:
> 520602640419 ("phy: qcom-qmp: Raise qcom_qmp_phy_enable() polling delay")
>
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
Merging of this patch got delayed. Bjorn, Is it okay if this patch gets merged
in the next merge window and backported to stable releases then?
Thanks
Kishon
next prev parent reply other threads:[~2019-08-21 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 0:42 [PATCH] phy: qcom-qmp: Correct ready status, again Bjorn Andersson
2019-08-20 14:07 ` Marc Gonzalez
[not found] ` <20190806155040.0B54520C01@mail.kernel.org>
2019-08-21 0:23 ` Kishon Vijay Abraham I [this message]
2019-08-26 15:15 ` Bjorn Andersson
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=57556d09-e2db-dc00-45a9-cbb57da02319@ti.com \
--to=kishon@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vivek.gautam@codeaurora.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).