[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <trinity-8384790e-d2aa-4041-b4e9-aba1130d8577-1649500371045@3c-app-gmx-bap35>
Date: Sat, 9 Apr 2022 12:32:51 +0200
From: Frank Wunderlich <frank-w@...lic-files.de>
To: Heiko Stuebner <heiko@...ech.de>
Cc: Frank Wunderlich <linux@...web.de>,
linux-rockchip@...ts.infradead.org,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Peter Geis <pgwipeout@...il.com>,
Michael Riesch <michael.riesch@...fvision.net>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Aw: Re: [PATCH] arm64: dts: rockchip: Fix clocks for rk356x usb
> Gesendet: Samstag, 09. April 2022 um 12:23 Uhr
> Von: "Heiko Stuebner" <heiko@...ech.de>
> ok, so do you want to send a v2 including that change?
> Alternatively I can also add this change when applying.
imho the best way will be that peter includes my patch in his
"arm64: dts: rockchip: add rk356x dwc3 usb3 nodes"
https://patchwork.kernel.org/project/linux-rockchip/patch/20220408151237.3165046-4-pgwipeout@gmail.com/
i just posted the fix for those who want to test his series on 5.18 including himself.
but of course if this is not the right way, i post a v2.
> Also for educational purposes, the format for referencing a commit
> you're fixing would be
>
> Fixes: 33fb697ec7e5 ("usb: dwc3: Get clocks individually")
> Signed-off-by: ....
as the patch not really broke current mainline state, i thought Fixes-tag is not right.
Imho only the rk356x-usb-patch is not compatible with 5.18 due to this change, but this is not applied yet.
regards Frank
Powered by blists - more mailing lists