From: Jakub Kicinski <kuba@kernel.org>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Jan Karcher <jaka@linux.ibm.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Alexandra Winter <wintera@linux.ibm.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Thorsten Winkler <twinkler@linux.ibm.com>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Mahanta Jambigi <mjambigi@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
"D. Wythe" <alibuda@linux.alibaba.com>
Subject: Re: [PATCH net] MAINTAINERS: update smc section
Date: Wed, 25 Jun 2025 15:21:18 -0700 [thread overview]
Message-ID: <20250625152118.77fdd8fc@kernel.org> (raw)
In-Reply-To: <20250625235023.2c4a3e8d.pasic@linux.ibm.com>
On Wed, 25 Jun 2025 23:50:23 +0200 Halil Pasic wrote:
> Jakub, would a respin with
> s/+M: Mahanta/+R: Mahanta/
> and the necessary reordering work for you?
>
> I'm with you, we should observe those rules, not only because they are a
> community standard, but also because they make a ton of sense IMHO. So
> my proposal is to make Mahanta a reviewer and revisit the topic of making
> him a maintainer after none of those bullets apply to him.
Starting with a R: sounds like a good compromise, thanks!
next prev parent reply other threads:[~2025-06-25 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:50 [PATCH net] MAINTAINERS: update smc section Jan Karcher
2025-06-23 8:57 ` Wenjia Zhang
2025-06-24 7:13 ` D. Wythe
2025-06-24 12:50 ` Dust Li
2025-06-24 23:44 ` Jakub Kicinski
2025-06-25 21:50 ` Halil Pasic
2025-06-25 22:21 ` Jakub Kicinski [this message]
2025-06-26 6:59 ` Mahanta Jambigi
2025-06-25 4:50 ` Sidraya Jayagond
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=20250625152118.77fdd8fc@kernel.org \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--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=twinkler@linux.ibm.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 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.