Hi Bryan Brattlof,
On Tue, 10 Dec 2024 14:59:23 -0600, Bryan Brattlof wrote:
> While debugging an unrelated issue Bin noticed we've accidentally
> defined the redistributor range for the GIC-500 two times on the AM62x
> and AM62Ax.
>
> This simple series removes the extra copy :)
>
> Happy Hacking
> ~Bryan
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-am62: remove duplicate GICR reg
commit: 72c691d77ea5d0c4636fd3e9f0ad80d813c7d1a7
[2/2] arm64: dts: ti: k3-am62a: remove duplicate GICR reg
commit: 6f0232577e260cdbc25508e27bb0b75ade7e7ebc
I have added the Fixes tag on your behalf this time around. Also the
reported-tag does'nt have a Closes link, which I understand is because
the report was internal. it does cause a checkpatch warning, which
would be useful to state in the diffstat section. Please take care of these
next time.
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
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
