сб, 29 серп. 2026 р. о 18:54 Tom Rini <[email protected]> пише: > > On Sat, Aug 29, 2026 at 06:13:27PM +0300, Svyatoslav Ryhel wrote: > > Hello Tom! > > > > сб, 29 серп. 2026 р. о 04:50 Tom Rini <[email protected]> пише: > > > > > > Update the main MAINTAINERS entry for Tegra to make use of the "N:" > > > syntax to catch everything with tegra in the filename. This lets us > > > remove the incorrect board config header entries for a large number of > > > platforms while still having the used header files have a maintainer be > > > found. Furthermore, correct some platform MAINTAINERS files that other > > > obvious issues (such as .dtb rather than .dts in listings). > > > > > > Signed-off-by: Tom Rini <[email protected]> > > > --- > > > Cc: Michal Simek <[email protected]> > > > Cc: Thierry Reding <[email protected]> > > > Cc: Svyatoslav Ryhel <[email protected]> > > > > > > This is slightly different than Michal's version because it adds the "N" > > > entry for Tegra overall and so catches include/configs/tegra.h which all > > > of the boards which had their include/configs/ line removed actually > > > use. > > > > That is smart. You don't need to replace device specific header with > > tegra.h in some files, you can just drop them. Thank you! > > My thought process on keeping them was that if a change is made to the > header then all of the board maintainers should get cc'd in case the > change impacts them. I can drop them if you still prefer in v3 however. >
I am pretty sure that include/configs/tegra.h is unlikely to be changed since it contains generic properties for all SoC generations. Even if it is changed, only SoC specific stuff is allowed there and device specific adjustment will require creation of device header. There are a few devices with non-generic header, mot.h and apalis-tk1.h come to my mind as an example. > -- > Tom
