From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Wenjia Zhang <wenjia@linux.ibm.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux390-list@tuxmaker.boeblingen.de.ibm.com,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
aswin@linux.ibm.com, Alexandra Winter <wintera@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Wen Gu <guwen@linux.alibaba.com>,
"D. Wythe" <alibuda@linux.alibaba.com>,
Tony Lu <tonylu@linux.alibaba.com>,
Dust Li <dust.li@linux.alibaba.com>
Subject: Re: [PATCH net-next] MAINTAINERS: Update SHARED MEMORY COMMUNICATIONS (SMC) maintainer entries
Date: Wed, 22 Jul 2026 12:06:35 +0100 [thread overview]
Message-ID: <453f43c3-e27f-4688-88db-19cc7f668f94@linux.dev> (raw)
In-Reply-To: <20260722085705.56755-1-wenjia@linux.ibm.com>
On 22/07/2026 09:57, Wenjia Zhang wrote:
> Due to a change in responsibilities, I can no longer serve as an SMC
> maintainer and need to be removed from the MAINTAINERS list.
>
> To reflect these organizational changes, promote Mahanta Jambigi
> <mjambigi@linux.ibm.com> from reviewer to maintainer.
>
> Signed-off-by: Wenjia Zhang <wenjia@linux.ibm.com>
> ---
> Kernels.code-workspace | 1 +
> MAINTAINERS | 3 +--
> file | 0
> 3 files changed, 2 insertions(+), 2 deletions(-)
> create mode 100644 Kernels.code-workspace
> create mode 100644 file
>
> diff --git a/Kernels.code-workspace b/Kernels.code-workspace
> new file mode 100644
> index 000000000000..9e26dfeeb6e6
> --- /dev/null
> +++ b/Kernels.code-workspace
> @@ -0,0 +1 @@
> +{}
this is not needed part...
> \ No newline at end of file
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1ab8736850ea..f60ccc62e710 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -24631,8 +24631,7 @@ SHARED MEMORY COMMUNICATIONS (SMC) SOCKETS
> M: D. Wythe <alibuda@linux.alibaba.com>
> M: Dust Li <dust.li@linux.alibaba.com>
> M: Sidraya Jayagond <sidraya@linux.ibm.com>
> -M: Wenjia Zhang <wenjia@linux.ibm.com>
> -R: Mahanta Jambigi <mjambigi@linux.ibm.com>
> +M: Mahanta Jambigi <mjambigi@linux.ibm.com>
> R: Tony Lu <tonylu@linux.alibaba.com>
> R: Wen Gu <guwen@linux.alibaba.com>
> L: linux-rdma@vger.kernel.org
> diff --git a/file b/file
> new file mode 100644
> index 000000000000..e69de29bb2d1
next prev parent reply other threads:[~2026-07-22 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 8:57 [PATCH net-next] MAINTAINERS: Update SHARED MEMORY COMMUNICATIONS (SMC) maintainer entries Wenjia Zhang
2026-07-22 11:01 ` Mahanta Jambigi
2026-07-22 11:06 ` Vadim Fedorenko [this message]
2026-07-22 12:11 ` Wenjia Zhang
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=453f43c3-e27f-4688-88db-19cc7f668f94@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=agordeev@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=aswin@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390-list@tuxmaker.boeblingen.de.ibm.com \
--cc=mjambigi@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=sidraya@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.com \
/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