Message ID | 20230424173623.477577-1-nm@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | arm64: dts: ti: k3-j7200: Fixes for various dtbs_checks warnings | expand |
On 12:36-20230424, Nishanth Menon wrote: > Hi, > > Few fixups for j7200 dtbs_check warnings. > > Bootlog: https://gist.github.com/nmenon/6a37fca2f05633b7153e661d2516deab > > NOTE: lets see the discussion summary of [1] to see where to take this > series, but, I will put it out here in the list for discussion anyways. > > [1] https://lore.kernel.org/all/76da0b98-3274-b047-db11-ecabc117ae11@ti.com/ > > Nishanth Menon (3): > arm64: dts: ti: k3-j7200-mcu-wakeup: Remove 0x unit address prefix > from nodename > arm64: dts: ti: k3-j7200-mcu-wakeup: Switch mcu_syscon to > ti,j721e-system-controller > arm64: dts: ti: k3-j7200-mcu-wakeup: Split fss node up > > .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 29 ++++++++++++------- > 1 file changed, 19 insertions(+), 10 deletions(-) > After looking a bit closer at this, lets drop this series. For the pinctrl fixup: Please pick up https://lore.kernel.org/all/20230510091850.28881-1-tony@atomide.com/ instead As discussed in https://lore.kernel.org/all/20230605205220.rjmcsi5tjn4auqa7@arose/ we can look at fss and syscon cleanup in the next kernel rev once the dependencies are sorted out.
Hi Nishanth Menon, On Mon, 24 Apr 2023 12:36:20 -0500, Nishanth Menon wrote: > Few fixups for j7200 dtbs_check warnings. > > Bootlog: https://gist.github.com/nmenon/6a37fca2f05633b7153e661d2516deab > > NOTE: lets see the discussion summary of [1] to see where to take this > series, but, I will put it out here in the list for discussion anyways. > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [1/3] arm64: dts: ti: k3-j7200-mcu-wakeup: Remove 0x unit address prefix from nodename commit: 4c3cdac1955a5274a42d915e98827ba0f136c286 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git -- Vignesh