linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Marko <robert.marko@sartura.hr>
To: Vinod Koul <vkoul@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	robh+dt@kernel.org, Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, John Crispin <john@phrozen.org>,
	Luka Perkov <luka.perkov@sartura.hr>
Subject: Re: [PATCH v7 3/3] ARM: dts: qcom: ipq4019: add USB devicetree nodes
Date: Fri, 29 May 2020 11:36:09 +0200	[thread overview]
Message-ID: <CA+HBbNEiB+o4KxonAu4-ra+P11Yb649v6AFaPjFc8JQDQ8T=CA@mail.gmail.com> (raw)
In-Reply-To: <20200504073914.GQ1375924@vkoul-mobl>

On Mon, May 4, 2020 at 9:39 AM Vinod Koul <vkoul@kernel.org> wrote:
>
> On 03-05-20, 22:18, Robert Marko wrote:
> > From: John Crispin <john@phrozen.org>
> >
> > Since we now have driver for the USB PHY, lets add the necessary nodes to DTSI.
>
> Reviewed-by: Vinod Koul <vkoul@kernel.org>
>
> Bjorn, I have picked the phy and dt binding, feel free to apply this one
>
> Thanks
> --
> ~Vinod

Any chance of this landing into 5.7?
Driver and bindings have been merged, but I don't see DT nodes queued.

Regards,
Robert

  reply	other threads:[~2020-05-29  9:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-03 20:18 [PATCH v7 1/3] phy: add driver for Qualcomm IPQ40xx USB PHY Robert Marko
2020-05-03 20:18 ` [PATCH v7 2/3] dt-bindings: phy-qcom-ipq4019-usb: add binding document Robert Marko
2020-05-04  7:37   ` Vinod Koul
2020-05-03 20:18 ` [PATCH v7 3/3] ARM: dts: qcom: ipq4019: add USB devicetree nodes Robert Marko
2020-05-04  7:39   ` Vinod Koul
2020-05-29  9:36     ` Robert Marko [this message]
2020-06-09 14:45       ` Robert Marko
2020-06-09 16:19         ` Vinod Koul
2020-08-06 11:06           ` Robert Marko
2020-05-03 20:21 ` [PATCH v7 1/3] phy: add driver for Qualcomm IPQ40xx USB PHY John Crispin
2020-05-04  7:37 ` Vinod Koul

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='CA+HBbNEiB+o4KxonAu4-ra+P11Yb649v6AFaPjFc8JQDQ8T=CA@mail.gmail.com' \
    --to=robert.marko@sartura.hr \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=john@phrozen.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luka.perkov@sartura.hr \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@kernel.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).