mbox series

[v2,0/2] Fix UART pin type and macro type

Message ID 20240415095605.3547933-1-u-kumar1@ti.com (mailing list archive)
Headers show
Series Fix UART pin type and macro type | expand

Message

Kumar, Udit April 15, 2024, 9:56 a.m. UTC
This series fixes UART pin mux for J784s4-evm and am69.
Along with replacing pin mux macro of J784S4 SOC instead of J721S2.

Test logs
https://gist.github.com/uditkumarti/a28ec171732e32c16b2666c27093c115

For fixes, these errors should be caught during review but missed due to
cross reference is taken from tool's output.
Note to self, don't always rely on tool's output while reviewing the patch.


Change logs:
Changes in v2:
Splitting patch series into two as refactoring and fixes,
This series is for fixes, refactoring will be sent later
Link of v1: https://lore.kernel.org/all/20240415063329.3286600-1-u-kumar1@ti.com/


Udit Kumar (2):
  arm64: dts: ti: k3-j784s4-evm: Fix UART pin type and macro type
  arm64: dts: ti: k3-am69-sk: Fix UART pin type and macro type

 arch/arm64/boot/dts/ti/k3-am69-sk.dts    | 12 ++++++------
 arch/arm64/boot/dts/ti/k3-j784s4-evm.dts |  8 ++++----
 2 files changed, 10 insertions(+), 10 deletions(-)

Comments

Nishanth Menon April 26, 2024, 10:39 p.m. UTC | #1
Hi Udit Kumar,

On Mon, 15 Apr 2024 15:26:03 +0530, Udit Kumar wrote:
> This series fixes UART pin mux for J784s4-evm and am69.
> Along with replacing pin mux macro of J784S4 SOC instead of J721S2.
> 
> Test logs
> https://gist.github.com/uditkumarti/a28ec171732e32c16b2666c27093c115
> 
> For fixes, these errors should be caught during review but missed due to
> cross reference is taken from tool's output.
> Note to self, don't always rely on tool's output while reviewing the patch.
> 
> [...]

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/2] arm64: dts: ti: k3-j784s4-evm: Fix UART pin type and macro type
      commit: d79fc91456338f42e9066cff91e3b4ea174986d4
[2/2] arm64: dts: ti: k3-am69-sk: Fix UART pin type and macro type
      commit: e1818f04eff632bad803f85d24dbfbfa3ddb5218

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