All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v2 6/7] MAINTAINERS: Removed files
Date: Mon, 31 Aug 2026 17:32:06 +0200	[thread overview]
Message-ID: <c34aa04d-bedf-41ef-90cc-6384882cac07@amd.com> (raw)
In-Reply-To: <20260831151641.GR3959812@bill-the-cat>



On 8/31/26 17:16, Tom Rini wrote:
> On Mon, Aug 31, 2026 at 08:40:23AM +0200, Michal Simek wrote:
>>
>>
>> On 8/29/26 03:50, Tom Rini wrote:
>>> Correct MAINTAINERS entries for files that have been removed. In most
>>> cases this is because a given platform has moved to using OF_UPSTREAM
>>> and so the local version of the file does not exist. In other cases,
>>> sample defconfigs have either been merged or simply removed.
>>>
>>> Signed-off-by: Tom Rini <trini@konsulko.com>
>>> ---
>>> Cc: Michal Simek <michal.simek@amd.com>
>>> ---
>>>    board/LaCie/net2big_v2/MAINTAINERS             |  4 ----
>>>    board/LaCie/netspace_v2/MAINTAINERS            |  6 ------
>>>    board/Synology/ds116/MAINTAINERS               |  1 -
>>>    board/altera/stratix10-socdk/MAINTAINERS       |  1 -
>>>    board/atmel/at91sam9260ek/MAINTAINERS          |  1 -
>>>    board/beacon/beacon-rzg2m/MAINTAINERS          |  3 ---
>>>    board/embest/mx6boards/MAINTAINERS             |  1 -
>>>    board/gardena/smart-gateway-mt7688/MAINTAINERS |  1 -
>>>    board/gateworks/gw_ventana/MAINTAINERS         |  6 ------
>>>    board/ge/bx50v3/MAINTAINERS                    |  3 ---
>>>    board/intel/agilex-socdk/MAINTAINERS           |  1 -
>>>    board/intel/agilex7m-socdk/MAINTAINERS         |  1 -
>>>    board/intel/n5x-socdk/MAINTAINERS              |  1 -
>>>    board/khadas/khadas-edge2-rk3588s/MAINTAINERS  |  1 -
>>>    board/kontron/sl-mx6ul/MAINTAINERS             |  7 +++----
>>>    board/mediatek/mt7981/MAINTAINERS              |  2 --
>>>    board/mediatek/mt7986/MAINTAINERS              |  4 ----
>>>    board/nxp/imx93_evk/MAINTAINERS                |  1 -
>>>    board/nxp/ls1012afrdm/MAINTAINERS              | 12 ++++--------
>>>    board/nxp/ls1012aqds/MAINTAINERS               |  1 -
>>>    board/nxp/ls1012ardb/MAINTAINERS               |  3 ---
>>>    board/nxp/ls1043aqds/MAINTAINERS               |  7 -------
>>>    board/nxp/ls1043ardb/MAINTAINERS               |  6 ------
>>>    board/nxp/ls1046aqds/MAINTAINERS               |  7 -------
>>>    board/nxp/ls1046ardb/MAINTAINERS               |  7 -------
>>>    board/nxp/ls1088a/MAINTAINERS                  |  9 ---------
>>>    board/nxp/ls2080aqds/MAINTAINERS               |  4 ----
>>>    board/nxp/ls2080ardb/MAINTAINERS               |  6 ------
>>>    board/nxp/lx2160a/MAINTAINERS                  |  2 --
>>>    board/nxp/mpc837xerdb/MAINTAINERS              |  1 -
>>>    board/nxp/mx6slevk/MAINTAINERS                 |  2 --
>>>    board/nxp/p2041rdb/MAINTAINERS                 |  3 ---
>>>    board/nxp/t104xrdb/MAINTAINERS                 | 13 -------------
>>>    board/nxp/t208xqds/MAINTAINERS                 |  5 -----
>>>    board/nxp/t208xrdb/MAINTAINERS                 |  1 -
>>>    board/phytec/phycore_am68x/MAINTAINERS         |  1 -
>>>    board/polyhex/imx8mp_debix_model_a/MAINTAINERS |  1 -
>>>    board/renesas/blanche/MAINTAINERS              |  1 -
>>>    board/seeed/linkit-smart-7688/MAINTAINERS      |  1 -
>>>    board/sunxi/MAINTAINERS                        |  2 --
>>>    board/toradex/colibri-imx6ull/MAINTAINERS      |  1 -
>>>    board/traverse/ten64/MAINTAINERS               |  1 -
>>>    board/xilinx/zynqmp/MAINTAINERS                |  1 -
>>>    board/zyxel/nsa325/MAINTAINERS                 |  3 ---
>>>    44 files changed, 7 insertions(+), 139 deletions(-)
>>
>> Perfect. Thanks. It depends which tree you will apply this
>> but I will keep my eyes on it and will rebase my changes on the top of it.
>>
>> Acked-by: Michal Simek <michal.simek@amd.com>
> 
> Note that this replaces your series that updated the general MAINTAINERS
> files. The series to consolidate the various tress you own still applies
> on its own and you should pick that up when ready :)
> 

Understood. Will just rebase to see that all things have been catched.

Thanks,
Michal




  reply	other threads:[~2026-08-31 15:32 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
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 [this message]
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=c34aa04d-bedf-41ef-90cc-6384882cac07@amd.com \
    --to=michal.simek@amd.com \
    --cc=trini@konsulko.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.