Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CA+G9fYtnwFVPQxgHOU2Bi9y5+q4sSsww47yxK+_3ZAQ9=kyhUg@mail.gmail.com>
 <20200219013824.GB8602@b29397-desktop> <20200219024534.GB10078@jackp-linux.qualcomm.com>
 <CAHp75VfY1Y-jNr=YTfAO+eUOy3xUy9+AgtyJuhEk2ngrxMg5JA@mail.gmail.com> <c39584b0-302e-d1bb-2e97-ffc017755bf2@st.com>
In-Reply-To: <c39584b0-302e-d1bb-2e97-ffc017755bf2@st.com>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Wed, 19 Feb 2020 13:28:05 +0200
Message-ID: <CAHp75VdDu678oL9VU8ea=A89O5L-5pPwkp8SOuySw+bCmtsAxA@mail.gmail.com>
Subject: Re: msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi
To:     Alexandre Torgue <alexandre.torgue@st.com>
Cc:     Jack Pham <jackp@codeaurora.org>, Peter Chen <peter.chen@nxp.com>,
        Naresh Kamboju <naresh.kamboju@linaro.org>,
        "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
        Linux-Next Mailing List <linux-next@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Feb 19, 2020 at 12:00 PM Alexandre Torgue
<alexandre.torgue@st.com> wrote:
> On 2/19/20 10:23 AM, Andy Shevchenko wrote:
> > On Wed, Feb 19, 2020 at 4:46 AM Jack Pham <jackp@codeaurora.org> wrote:
> >>
> >> On Wed, Feb 19, 2020 at 01:38:22AM +0000, Peter Chen wrote:
> >>> On 20-02-17 14:02:57, Naresh Kamboju wrote:
> >>>> arm64 APQ 8016 SBC ( Dragonboard 410c)  device running Linux next boot
> >>>> failed due to below error.

...

> >> Probably same cause as for this:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=206435
> >
> > Yes, it's the same. I dunno why no fix yet available.
> >
>
> Kishon has posted a patch yesterday for device link issue in phy core.

Ah, good to know! (Seems it hasn't made Linux Next yet, though)

> Please see:
>
> https://lkml.org/lkml/2020/2/18/272

Hint: use lore.kernel.org instead, much better if one would like to
reply / apply / etc.

-- 
With Best Regards,
Andy Shevchenko