On Sat, 29 Aug 2026 09:34:18 -0500, Bryan Brattlof wrote:

> While updating the check_maintainers_files.sh it was noticed many of the
> MAINTAINERS entries in board/ti/ are out of date[0].
> 
> So this series aims as trying to update all entries by splitting each
> board into their own block, sorting the F: entries, correcting any file
> names, and finally adding any missing files I noticed.
> 
> [...]

Applied to u-boot/main, thanks!

[01/14] board: ti: sort file entries in MAINTAINERS files
        commit: 4231d50c067003169cfed53b6dce753211aa46ed
[02/14] board: ti: correct names in MAINTAINERS file
        commit: f1a98de73e3a8e9ceeb93e04ab218687648fd5ab
[03/14] board: ti: am62x: split board variants into separate maintainer entries
        commit: 81e8aa8d426efc5f9ba87af4cf79846b0bc96863
[04/14] board: ti: am64x: split the EVM and SK board entries
        commit: 8944fe91356188e4caba14421b22083b2f453345
[05/14] board: ti: j721e: split boards into separate maintainer entries
        commit: 5a08a113fed2261a748f574aeaf2c8d769a94794
[06/14] board: ti: j721s2: split boards into separate maintainer entries
        commit: 7ce170d9507d2add5ab02182fe1c2cd4149ace32
[07/14] board: ti: am62x: add files to MAINTAINERS entries
        commit: 774e11aaebd373979d4525c66a052c9c32bdd31d
[08/14] board: ti: am62ax: update MAINTAINERS entries
        commit: 2954465b7de8588a2c3b64ae4c0dbbb16abd52d9
[09/14] board: ti: am62dx: update MAINTAINERS entries
        commit: 7ee8164bd0682e01a7bfe315d81ac0929051c3ff
[10/14] board: ti: am62px: update MAINTAINERS entries
        commit: c305e0cd6155c932202e290a032491161df6d803
[11/14] board: ti: j7200: update MAINTAINERS entries
        commit: f2e95ad4b02afe8a671cf2905f111d708c4e4b46
[12/14] board: ti: j721e: update MAINTAINERS entries
        commit: 5579e96029bbe5029cf2975462ba477774bffc73
[13/14] board: ti: j721s2: update MAINTAINERS entries
        commit: f6959b909fa564bfbb78976c7e3a82b3fd8776ab
[14/14] board: ti: j722s: update the MAINTAINERS entry
        commit: 23c2aedbd786f7fc13b4b8c11b1194b19d51c741
-- 
Tom


Reply via email to