From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Cc: dinguyen@kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL 2/2] MAINTAINERS: socfpga: update for v7.4
Date: Thu, 8 Oct 2026 11:48:16 -0500 [thread overview]
Message-ID: <20261008164816.566624-1-dinguyen@kernel.org> (raw)
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/socfpga_maintainer_update_for_v7.4
for you to fetch changes up to 96e948e9811dcb68f513e1d6445e22999f8d099b:
MAINTAINERS: Drop arm64 dts/intel path from ARM/SOCFPGA ARCHITECTURE (2026-10-05 10:13:13 -0500)
----------------------------------------------------------------
SoCFPGA MAINTAINERS update for for v7.4
- Drop the arm64/boot/dts/intel from Dinh Nguyen's entry since
all Altera's SoCFPGA files have been moved to dts/altera
----------------------------------------------------------------
Chiam, Evon (1):
MAINTAINERS: Drop arm64 dts/intel path from ARM/SOCFPGA ARCHITECTURE
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
reply other threads:[~2026-10-08 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261008164816.566624-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox