Hi all,
The following commits are also in the char-misc tree as different
commits (but the same patches):
213700a8b96f ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
76ac787cd671 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
These are commits
8258d997b874 ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
5ccf40288ca0 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
in the char-misc tree.
--
Cheers,
Stephen Rothwell
Hi!
2023-06-02 at 05:31, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the char-misc tree as different
> commits (but the same patches):
>
> 213700a8b96f ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
> 76ac787cd671 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
>
> These are commits
>
> 8258d997b874 ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
> 5ccf40288ca0 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
>
> in the char-misc tree.
I didn't think this was an issue, so I have now removed them from the
mux for-next branch.
Going forward, I will try to time the removal from the mux for-next branch
when I hear from Greg that the patches have hit char-misc/for-next.
The reason for all this is that the patch-stream for mux is just a trickle,
so Greg is not pulling my tree, and I instead send patches. I still want to
see how patches fare in -next before I pass them on, so this is probably
going to happen again from time to time.
Cheers,
Peter