From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-arm-msm-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 9F902C433EF
	for <linux-arm-msm@archiver.kernel.org>; Fri, 17 Jun 2022 00:38:16 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229832AbiFQAiP (ORCPT
        <rfc822;linux-arm-msm@archiver.kernel.org>);
        Thu, 16 Jun 2022 20:38:15 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51268 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229734AbiFQAiP (ORCPT
        <rfc822;linux-arm-msm@vger.kernel.org>);
        Thu, 16 Jun 2022 20:38:15 -0400
Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D296953C75
        for <linux-arm-msm@vger.kernel.org>; Thu, 16 Jun 2022 17:38:14 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by dfw.source.kernel.org (Postfix) with ESMTPS id 70D0C6194A
        for <linux-arm-msm@vger.kernel.org>; Fri, 17 Jun 2022 00:38:14 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id B9492C34114;
        Fri, 17 Jun 2022 00:38:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1655426293;
        bh=4zSipTb8ys2Cxh8WgYAx7pfSzuRK55TeyzQ58OmVuSU=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=g2U6KnR3OYsG5SZVCg+0wvsuygu6ZTkrM/Hf8hon7dFgPACOYCHsmcjTRDljrn0L/
         CvX3vvtU4gE0DcPsOyaXT30nWi0MmsvakqSOEvHXKvPBBpV/Mmz/BdUEoPWeVhgkHp
         bhO6miAhuqMAZe65o1aYE8z41nLvawBjPnVzQeMG5GSsUNRnqO+pngcaWuO/5nQhs4
         IdrBOXBOHMcAOuLFZ4UJzo4Hx7/knJvDJXfIIuMHEQA949nLscyL3kagXx5bMltESI
         ruTrZTEtkT+yLg6ChAC16YjhUZbMZlAsTZgHT2dnwPdFp3X+s7HbbvSiWgYRrqId3g
         fRaCJoRX8Mf9g==
Date:   Thu, 16 Jun 2022 17:38:13 -0700
From:   Vinod Koul <vkoul@kernel.org>
To:     Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc:     Andy Gross <agross@kernel.org>,
        Bjorn Andersson <bjorn.andersson@linaro.org>,
        Kishon Vijay Abraham I <kishon@ti.com>,
        Philipp Zabel <p.zabel@pengutronix.de>,
        linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH 0/2] phy: qcom-qmp: fix QMP PCIe PHY init
Message-ID: <YqvM9e/CfJcrsC/E@matsya>
References: <20220610185542.3662484-1-dmitry.baryshkov@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220610185542.3662484-1-dmitry.baryshkov@linaro.org>
Precedence: bulk
List-ID: <linux-arm-msm.vger.kernel.org>
X-Mailing-List: linux-arm-msm@vger.kernel.org

On 10-06-22, 21:55, Dmitry Baryshkov wrote:
> These two patches fix PCIe PHY init after the previous QMP PHY rework
> ([1]). They were generated on top of phy/next, but I'm fine with them
> being squashed to the corresponding patches.

Applied, thanks

-- 
~Vinod