On Thu, Mar 24, 2022 at 10:01 PM Dave Airlie airlied@gmail.com wrote:
FYI, this breaks the DT bindings. The relevant patches didn't get reviewed nor run thru automated testing because their encoding was 'charset=y'[1]. (While email clients seem to just ignore that encoding, patchwork and b4 do not.) linux-next is still broken and has been since Mar 2[2]. v2 of the fixes[3] have been posted since Mar 9, and still aren't in linux-next.
It doesn't have to be fixed in this PR, but it needs to be fixed before rc1. Otherwise, no one can test their bindings using rc1. In general, there's no reason fixes need to wait until after rc1 as Chun-Kuang suggests[4].
With the conflicts that Linus merged, can we get this rebased onto Linus merge, and submitted to him?
I applied the series without issue on Linus' current tree aa5b537b0ecc ("Merge tag 'riscv-for-linus-5.18-mw0' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux") and confirmed the binding errors are fixed. Must be some difference in what's in the Mediatek PR...
b4 shazam -lsSt 20220309134702.9942-1-jason-jh.lin@mediatek.com
Rob