Hello Everyone!

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.

Happy Hacking
~Bryan

[0] https://lore.kernel.org/all/[email protected]/

Signed-off-by: Bryan Brattlof <[email protected]>
---
Bryan Brattlof (14):
      board: ti: sort file entries in MAINTAINERS files
      board: ti: correct names in MAINTAINERS file
      board: ti: am62x: split board variants into separate maintainer entries
      board: ti: am64x: split the EVM and SK board entries
      board: ti: j721e: split boards into separate maintainer entries
      board: ti: j721s2: split boards into separate maintainer entries
      board: ti: am62x: add files to MAINTAINERS entries
      board: ti: am62ax: update MAINTAINERS entries
      board: ti: am62dx: update MAINTAINERS entries
      board: ti: am62px: update MAINTAINERS entries
      board: ti: j7200: update MAINTAINERS entries
      board: ti: j721e: update MAINTAINERS entries
      board: ti: j721s2: update MAINTAINERS entries
      board: ti: j722s: update the MAINTAINERS entry

 board/ti/am62ax/MAINTAINERS | 20 ++++++++++---
 board/ti/am62dx/MAINTAINERS | 17 +++++++++--
 board/ti/am62px/MAINTAINERS | 20 ++++++++++---
 board/ti/am62x/MAINTAINERS  | 72 +++++++++++++++++++++++++++++++++++++++++----
 board/ti/am64x/MAINTAINERS  | 15 ++++++++--
 board/ti/am65x/MAINTAINERS  |  2 +-
 board/ti/j7200/MAINTAINERS  | 14 ++++++---
 board/ti/j721e/MAINTAINERS  | 32 ++++++++++++++++----
 board/ti/j721s2/MAINTAINERS | 41 +++++++++++++++++---------
 board/ti/j722s/MAINTAINERS  | 15 +++++++---
 board/ti/j784s4/MAINTAINERS | 40 ++++++++++++++-----------
 11 files changed, 223 insertions(+), 65 deletions(-)
---
base-commit: 67a095a6896828056e4a1a0ba0e9bb20f5595c59
change-id: 20260826-maintainer-fixes-7fffff976733

Best regards,
--  
Bryan Brattlof <[email protected]>

Reply via email to