netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Sai Krishna <saikrishnag@marvell.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<sgoutham@marvell.com>, <richardcochran@gmail.com>
Subject: Re: [net PATCH 0/7] octeontx2: Miscellaneous fixes
Date: Thu, 30 Mar 2023 10:48:16 -0700	[thread overview]
Message-ID: <20230330104816.29d6fc4e@kernel.org> (raw)
In-Reply-To: <20230329170619.183064-1-saikrishnag@marvell.com>

On Wed, 29 Mar 2023 22:36:12 +0530 Sai Krishna wrote:
> From: Sai Krishna <saikrishnag@marvell.com>
> To: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,         <pabeni@redhat.com>, <netdev@vger.kernel.org>,         <linux-kernel@vger.kernel.org>, <sgoutham@marvell.com>,         <richardcochran@gmail.com>
> CC: Sai Krishna <saikrishnag@marvell.com>

First of all, does the maintainers file need to be updated?

This driver has a crazy number of maintainers:

MARVELL OCTEONTX2 RVU ADMIN FUNCTION DRIVER
M:	Sunil Goutham <sgoutham@marvell.com>
M:	Linu Cherian <lcherian@marvell.com>
M:	Geetha sowjanya <gakula@marvell.com>
M:	Jerin Jacob <jerinj@marvell.com>
M:	hariprasad <hkelam@marvell.com>
M:	Subbaraya Sundeep <sbhatta@marvell.com>
L:	netdev@vger.kernel.org
S:	Supported
F:	Documentation/networking/device_drivers/ethernet/marvell/octeontx2.rst
F:	drivers/net/ethernet/marvell/octeontx2/af/

And yet the person posting patches for the company is not on that list?!
Please clean this up, or CC authors of patches on the fixes.

  parent reply	other threads:[~2023-03-30 17:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 17:06 [net PATCH 0/7] octeontx2: Miscellaneous fixes Sai Krishna
2023-03-29 17:06 ` [net PATCH 1/7] octeontx2-af: Secure APR table update with the lock Sai Krishna
2023-03-30  5:55   ` Leon Romanovsky
2023-03-30  6:56     ` [EXT] " Geethasowjanya Akula
2023-03-30  7:16       ` Leon Romanovsky
2023-03-31  8:56         ` Geethasowjanya Akula
2023-04-03 13:08           ` Leon Romanovsky
2023-03-29 17:06 ` [net PATCH 2/7] octeontx2-af: Fix start and end bit for scan config Sai Krishna
2023-03-30  6:12   ` Leon Romanovsky
2023-03-29 17:06 ` [net PATCH 3/7] octeontx2-af: Add validation for lmac type Sai Krishna
2023-03-30  6:18   ` Leon Romanovsky
2023-03-30 10:08     ` [EXT] " Sai Krishna Gajula
2023-03-30 10:13     ` Sai Krishna Gajula
2023-03-29 17:06 ` [net PATCH 4/7] octeontx2-af: Update correct mask to filter IPv4 fragments Sai Krishna
2023-03-30  6:19   ` Leon Romanovsky
2023-03-29 17:06 ` [net PATCH 5/7] octeontx2-af: Fix issues with NPC field hash extract Sai Krishna
2023-03-30  6:20   ` Leon Romanovsky
2023-03-30 17:58     ` Sai Krishna Gajula
2023-03-29 17:06 ` [net PATCH 6/7] octeontx2-af: Skip PFs if not enabled Sai Krishna
2023-03-29 17:06 ` [net PATCH 7/7] octeontx2-pf: Disable packet I/O for graceful exit Sai Krishna
2023-03-30  6:23   ` Leon Romanovsky
2023-03-30 17:48 ` Jakub Kicinski [this message]
2023-04-05  6:15   ` [net PATCH 0/7] octeontx2: Miscellaneous fixes Sai Krishna Gajula

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=20230330104816.29d6fc4e@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=saikrishnag@marvell.com \
    --cc=sgoutham@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;
as well as URLs for NNTP newsgroup(s).