From: Michal Simek <monstr@monstr.eu>
To: SoC Team <soc@kernel.org>
Cc: linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] arm64: ZynqMP SoC changes for v6.9
Date: Mon, 26 Feb 2024 13:42:27 +0100 [thread overview]
Message-ID: <CAHTX3d+NGUJhKXxGwskSOf6U9P0Nd9rnroFczD8X2mLhFgcm0Q@mail.gmail.com> (raw)
Hi Arnd,
We discussed this change via the side channel with Abhyuday and he is
fine with this change but he is not willing (after discussion with his
current employer and for whatever else reason) to even ack this
change. Listed xilinx email is no longer working too. That's why based
on our talk I am sending a single patch to change the maintainer of
Xilinx event management driver to unblock this situation.
Thanks,
Michal
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
https://github.com/Xilinx/linux-xlnx.git tags/zynqmp-soc-for-6.9
for you to fetch changes up to be53a3b3bc58bb5be6c4228523b071b345d5574b:
soc: xilinx: update maintainer of event manager driver (2024-01-23
14:57:47 +0100)
----------------------------------------------------------------
arm64: ZynqMP SoC changes for 6.9
- Update maintainer for event manager
----------------------------------------------------------------
Jay Buddhabhatti (1):
soc: xilinx: update maintainer of event manager driver
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
next reply other threads:[~2024-02-26 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 12:42 Michal Simek [this message]
2024-03-04 16:12 ` [GIT PULL] arm64: ZynqMP SoC changes for v6.9 patchwork-bot+linux-soc
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=CAHTX3d+NGUJhKXxGwskSOf6U9P0Nd9rnroFczD8X2mLhFgcm0Q@mail.gmail.com \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).