From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: kishon@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
Xu Yang <xu.yang_2@nxp.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] dtbs_check warning clean up against fsl,mxs-usbphy.yaml
Date: Tue, 29 Oct 2024 16:15:54 +0100 [thread overview]
Message-ID: <6099458.lOV4Wx5bFT@steina-w> (raw)
In-Reply-To: <172917937246.288841.15901592420939223719.b4-ty@kernel.org>
Hi Vinod,
Am Donnerstag, 17. Oktober 2024, 17:36:12 CET schrieb Vinod Koul:
>
> On Thu, 26 Sep 2024 15:39:46 +0800, Xu Yang wrote:
> > Some changes to clean up dtbs_check warning against fsl,mxs-usbphy.yaml.
> >
> > The first 4 patches are used to fix below warning, "nxp,sim" is only
> > needed by i.MX7ULP:
> > - 'nxp,sim' is a required property
> >
> > The last patch is used to fix below warning:
> > - fsl,tx-d-cal: 5 is less than the minimum of 79
> >
> > [...]
>
> Applied, thanks!
>
> [1/5] dt-bindings: phy: mxs-usb-phy: add imx8qxp compatible
> commit: 76b4f2a5cec59e842de4b5989eb990a2ee8cedf3
> [2/5] arm64: dts: imx8dxl-ss-conn: change usbphy1 compatible
> (no commit info)
> [3/5] arm64: dts: imx8qm: change usbphy1 compatible
> (no commit info)
> [4/5] arm64: dts: imx8qxp: change usbphy1 compatible
> (no commit info)
> [5/5] ARM: dts: imx6qdl: convert fsl,tx-d-cal to correct value
> (no commit info)
Did maybe something go wrong while merging? Only patch 1 has a commit SHA1
in this mail.
Also only patch 1 is available in linux-next
Thanks and best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2024-10-29 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 7:39 [PATCH 0/5] dtbs_check warning clean up against fsl,mxs-usbphy.yaml Xu Yang
2024-09-26 7:39 ` [PATCH 1/5] dt-bindings: phy: mxs-usb-phy: add imx8qxp compatible Xu Yang
2024-09-26 16:05 ` Conor Dooley
2024-09-26 7:39 ` [PATCH 2/5] arm64: dts: imx8dxl-ss-conn: change usbphy1 compatible Xu Yang
2024-11-01 8:06 ` Shawn Guo
2024-09-26 7:39 ` [PATCH 3/5] arm64: dts: imx8qm: " Xu Yang
2024-09-26 7:39 ` [PATCH 4/5] arm64: dts: imx8qxp: " Xu Yang
2024-09-26 7:39 ` [PATCH 5/5] ARM: dts: imx6qdl: convert fsl,tx-d-cal to correct value Xu Yang
2024-10-17 15:36 ` [PATCH 0/5] dtbs_check warning clean up against fsl,mxs-usbphy.yaml Vinod Koul
2024-10-29 15:15 ` Alexander Stein [this message]
2024-10-29 15:29 ` Frank Li
2024-10-29 15:41 ` [PATCH 0/5] dtbs_check warning clean up against fsl, mxs-usbphy.yaml Alexander Stein
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=6099458.lOV4Wx5bFT@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=vkoul@kernel.org \
--cc=xu.yang_2@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).