From: Tom Rini <trini@konsulko.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: u-boot@lists.u-boot-project.org,
Michal Simek <michal.simek@amd.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v2 2/7] MAINTAINERS: tegra: Update and correct entries
Date: Sat, 29 Aug 2026 09:54:33 -0600 [thread overview]
Message-ID: <20260829155433.GO3959812@bill-the-cat> (raw)
In-Reply-To: <CAPVz0n2EQAiqCGeDGosfrytB6908iPfvAt4JwNHtua6QE_ETOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
On Sat, Aug 29, 2026 at 06:13:27PM +0300, Svyatoslav Ryhel wrote:
> Hello Tom!
>
> сб, 29 серп. 2026 р. о 04:50 Tom Rini <trini@konsulko.com> пише:
> >
> > 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 <trini@konsulko.com>
> > ---
> > Cc: Michal Simek <michal.simek@amd.com>
> > Cc: Thierry Reding <treding@nvidia.com>
> > Cc: Svyatoslav Ryhel <clamor95@gmail.com>
> >
> > 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.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-08-29 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 1:50 [PATCH v2 0/7] Cleanup MAINTAINERS entries Tom Rini
2026-08-29 1:50 ` [PATCH v2 1/7] scripts: Check F: entries in all MAINTAINERS files Tom Rini
2026-08-29 1:50 ` [PATCH v2 2/7] MAINTAINERS: tegra: Update and correct entries Tom Rini
2026-08-29 15:13 ` Svyatoslav Ryhel
2026-08-29 15:54 ` Tom Rini [this message]
2026-08-29 16:05 ` Svyatoslav Ryhel
2026-08-29 16:12 ` Tom Rini
2026-08-29 1:50 ` [PATCH v2 3/7] MAINTAINERS: rockchip: Use N for rk3576-nanopi-r76s Tom Rini
2026-08-29 1:50 ` [PATCH v2 4/7] MAINTAINERS: Fix "typo" and similar incorrect entries Tom Rini
2026-08-29 1:50 ` [PATCH v2 5/7] MAINTAINERS: Correct entries missed during renames Tom Rini
2026-08-29 1:50 ` [PATCH v2 6/7] MAINTAINERS: Removed files Tom Rini
2026-08-29 20:16 ` Tony Dinh
2026-08-31 6:40 ` Michal Simek
2026-08-31 15:16 ` Tom Rini
2026-08-31 15:32 ` Michal Simek
2026-08-29 1:50 ` [PATCH v2 7/7] CI: Run scripts/check_maintainers_files.sh in the existing MAINTAINERS job Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260829155433.GO3959812@bill-the-cat \
--to=trini@konsulko.com \
--cc=clamor95@gmail.com \
--cc=michal.simek@amd.com \
--cc=treding@nvidia.com \
--cc=u-boot@lists.u-boot-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.