From: Marek Vasut via U-Boot <u-boot@lists.u-boot-project.org>
To: Carlo Caione <ccaione@baylibre.com>,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
u-boot@lists.u-boot-project.org
Cc: Ryder Lee <ryder.lee@mediatek.com>,
Weijie Gao <weijie.gao@mediatek.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Igor Belwon <igor.belwon@mentallysanemainliners.org>,
David Lechner <dlechner@baylibre.com>,
Julien Stephan <jstephan@baylibre.com>,
Marek Vasut <marex@denx.de>, Tom Rini <trini@konsulko.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Peng Fan <peng.fan@nxp.com>,
Jaehoon Chung <jh80.chung@samsung.com>
Subject: Re: [PATCH v5] usb: mtu3: support the upstream devicetree binding
Date: Wed, 5 Aug 2026 12:51:35 +0200 [thread overview]
Message-ID: <e86f4c8e-7043-4272-85d5-a3cb1b851a2e@mailbox.org> (raw)
In-Reply-To: <DKGY0BWU7SO0.3L78LYC856KGI@baylibre.com>
On 8/5/26 12:37 PM, Carlo Caione wrote:
> On Wed Aug 5, 2026 at 4:37 AM CEST, Marek Vasut wrote:
>> On 8/4/26 12:05 PM, Carlo Caione wrote:
>>
>> [...]
>>
>>> +++ b/doc/device-tree-bindings/usb/mediatek,mtu3.txt
>>
>> You could easily swap in Linux
>> Documentation/devicetree/bindings/usb/mediatek,mtu3.yaml and
>> Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml instead ,
>> and drop the mtu3.txt . But please do replace the binding documents in a
>> separate patch.
>
> Shouldn't we just drop both
> doc/device-tree-bindings/usb/mediatek,mtk-xhci.txt and
> doc/device-tree-bindings/usb/mediatek,mtu3.txt and automatically fall
> back onto the corresponding ones in dts/upstream/Bindings/usb?
Even better, thanks !
prev parent reply other threads:[~2026-08-05 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 10:05 [PATCH v5] usb: mtu3: support the upstream devicetree binding Carlo Caione
2026-08-05 2:37 ` Marek Vasut via U-Boot
2026-08-05 10:37 ` Carlo Caione
2026-08-05 10:51 ` Marek Vasut via U-Boot [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=e86f4c8e-7043-4272-85d5-a3cb1b851a2e@mailbox.org \
--to=u-boot@lists.u-boot-project.org \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=ccaione@baylibre.com \
--cc=chunfeng.yun@mediatek.com \
--cc=dlechner@baylibre.com \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=jstephan@baylibre.com \
--cc=marek.vasut@mailbox.org \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=ryder.lee@mediatek.com \
--cc=trini@konsulko.com \
--cc=weijie.gao@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.