From: Andrew Lunn <andrew@lunn.ch>
To: "Nimal Prabudoss [C]" <nprabudoss@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jmeneghi@redhat.com, mschmidt@redhat.com, manishc@marvell.com,
palok@marvell.com, spadol@marvell.com, jtaubepe@redhat.com
Subject: Re: [PATCH] MAINTAINERS: Update maintainers for QLogic ETHERNET drivers
Date: Fri, 23 Oct 2026 16:02:10 +0200 [thread overview]
Message-ID: <d1dcada0-9949-404e-b08a-7ed91d9d4e96@lunn.ch> (raw)
In-Reply-To: <20261023125409.1989-1-nprabudoss@marvell.com>
On Fri, Oct 23, 2026 at 06:24:08PM +0530, Nimal Prabudoss [C] wrote:
> From: Nimal Prabudoss <nprabudoss@marvell.com>
>
> Update maintainer list for BROADCOM BNX2 GIGABIT ETHERNET DRIVER
> and QLOGIC QL4xxx ETHERNET DRIVER to reflect current team structure.
Why Cc: the scsi list? Who do you expect to actually merge this?
> BROADCOM BNX2 GIGABIT ETHERNET DRIVER
> -M: Rasesh Mody <rmody@marvell.com>
> +M: Nimal Prabudoss <nprabudoss@marvell.com>
> +M: Sharad Padol <spadol@marvell.com>
~/linux/drivers/net/ethernet/broadcom$ git log --pretty=format:"%an" bnx2* | grep "Nimal"
~/linux/drivers/net/ethernet/broadcom$ git log --pretty=format:"%an" bnx2* | grep "Sharad"
~/linux/drivers/net/ethernet/broadcom$ git log --pretty=format:"%an" bnx2* | grep "Rasesh"
Rasesh Mody
Rasesh Mody
Rasesh Mody
We generally want Maintainers who have shown they can do the work,
posted patches, answered questions, know Mainline processes, and don't
spam other lists etc.
Maybe it would be better to leave it without Maintainers, at least
until you have reach the level Rasesh Mody achieved.
Andrew
next prev parent reply other threads:[~2026-10-23 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 12:54 Nimal Prabudoss [C]
2026-10-23 14:02 ` Andrew Lunn [this message]
2026-10-23 19:27 ` Jakub Kicinski
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=d1dcada0-9949-404e-b08a-7ed91d9d4e96@lunn.ch \
--to=andrew@lunn.ch \
--cc=jmeneghi@redhat.com \
--cc=jtaubepe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nprabudoss@marvell.com \
--cc=palok@marvell.com \
--cc=spadol@marvell.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
all inboxes | Powered by JetHome®