linux-kernel - Re: [PATCH] phy: qcom-qmp: Correct ready status, again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <57556d09-e2db-dc00-45a9-cbb57da02319@ti.com>
Date:   Wed, 21 Aug 2019 05:53:47 +0530
From:   Kishon Vijay Abraham I <kishon@...com>
To:     Sasha Levin <sashal@...nel.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>
CC:     <linux-arm-msm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <stable@...r.kernel.org>,
        Vivek Gautam <vivek.gautam@...eaurora.org>,
        Evan Green <evgreen@...omium.org>,
        Niklas Cassel <niklas.cassel@...aro.org>
Subject: Re: [PATCH] phy: qcom-qmp: Correct ready status, again

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