linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
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>
Subject: Re: msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi
Date: Wed, 19 Feb 2020 13:28:05 +0200	[thread overview]
Message-ID: <CAHp75VdDu678oL9VU8ea=A89O5L-5pPwkp8SOuySw+bCmtsAxA@mail.gmail.com> (raw)
In-Reply-To: <c39584b0-302e-d1bb-2e97-ffc017755bf2@st.com>

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

      reply	other threads:[~2020-02-19 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  8:32 msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi Naresh Kamboju
2020-02-19  1:38 ` Peter Chen
2020-02-19  2:45   ` Jack Pham
2020-02-19  9:23     ` Andy Shevchenko
2020-02-19 10:00       ` Alexandre Torgue
2020-02-19 11:28         ` Andy Shevchenko [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='CAHp75VdDu678oL9VU8ea=A89O5L-5pPwkp8SOuySw+bCmtsAxA@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=alexandre.torgue@st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jackp@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=peter.chen@nxp.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).