aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2025-07-23 22:21:51 +0200
committerArnd Bergmann <arnd@arndb.de>2025-07-23 22:21:51 +0200
commit4ec93a80d774bf6c62c8232d2a497ac761931649 (patch)
tree724068f5bd53e9ff6830556e83f2fec1e404be9a /tools/perf/scripts/python/Perf-Trace-Util/lib
parentMerge tag 'samsung-drivers-6.17' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into soc/dt (diff)
parentarm64: samsung: MAINTAINERS: Add Tesla FSD DTS to Exynos entry (diff)
downloadwireguard-linux-4ec93a80d774bf6c62c8232d2a497ac761931649.tar.xz
wireguard-linux-4ec93a80d774bf6c62c8232d2a497ac761931649.zip
Merge tag 'samsung-dt64-6.17-2' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux into soc/dt
Samsung DTS ARM64 changes for v6.17, part two Tesla FSD and Google GS101 DTS are handled via Samsung SoC tree, so the clean dtbs_check rule applies there as well - mention this in their maintainer entries. Also, include Tesla FSD DTS patterns in Samsung SoC tree to document how the patches actually travel. * tag 'samsung-dt64-6.17-2' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux: arm64: samsung: MAINTAINERS: Add Tesla FSD DTS to Exynos entry arm64: tesla/google: MAINTAINERS: Reference "SoC clean" maintainer profile Link: https://lore.kernel.org/r/20250723090455.25295-4-krzysztof.kozlowski@linaro.org Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib')
0 files changed, 0 insertions, 0 deletions