From: Vinod Koul <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Shawn Guo <shawn.guo@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Loic Poulain <loic.poulain@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: phy: qcom,qmp: Add QCM2290 USB3 PHY
Date: Fri, 1 Oct 2021 13:49:47 +0530 [thread overview]
Message-ID: <YVbEo4i5T63O+RnC@matsya> (raw)
In-Reply-To: <1632745399.282824.3097156.nullmailer@robh.at.kernel.org>
On 27-09-21, 07:23, Rob Herring wrote:
> On Mon, 27 Sep 2021 14:48:28 +0800, Shawn Guo wrote:
> > Add support for USB3 PHY found on Qualcomm QCM2290 SoC.
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > .../devicetree/bindings/phy/qcom,qmp-phy.yaml | 27 +++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
>
> Running 'make dtbs_check' with the schema in this patch gives the
> following warnings. Consider if they are expected or the schema is
> incorrect. These may not be new warnings.
>
> Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> This will change in the future.
Shawn has fixed it at: https://lore.kernel.org/r/20210929034253.24570-1-shawn.guo@linaro.org
I guess you are okay with this patch, if not do let me know...
--
~Vinod
next prev parent reply other threads:[~2021-10-01 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 6:48 [PATCH 0/2] Add QCM2290 USB3 PHY support Shawn Guo
2021-09-27 6:48 ` [PATCH 1/2] dt-bindings: phy: qcom,qmp: Add QCM2290 USB3 PHY Shawn Guo
2021-09-27 12:23 ` Rob Herring
2021-10-01 8:19 ` Vinod Koul [this message]
2021-10-04 18:14 ` Rob Herring
2021-09-27 6:48 ` [PATCH 2/2] phy: qcom-qmp: Add QCM2290 USB3 PHY support Shawn Guo
2021-10-05 7:50 ` [PATCH 0/2] " 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=YVbEo4i5T63O+RnC@matsya \
--to=vkoul@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=loic.poulain@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.guo@linaro.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).