From: Jakub Kicinski <kuba@kernel.org>
To: Veerasenareddy Burru <vburru@marvell.com>
Cc: Sathesh B Edara <sedara@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Satananda Burla <sburla@marvell.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH] MAINTAINERS: update email addresses of octeon_ep driver maintainers
Date: Tue, 20 Jun 2023 09:18:00 -0700 [thread overview]
Message-ID: <20230620091800.736bf269@kernel.org> (raw)
In-Reply-To: <20230616101229.1e7339f0@kernel.org>
On Fri, 16 Jun 2023 10:12:29 -0700 Jakub Kicinski wrote:
> > Sathesh will also be maintaining and submitting the changes for
> > octeon_ep drivers, going forward.
> >
> > Is the right way for this is, add Sathesh to MAINTAINERS list along
> > with his first patch/patchset submission ?
>
> The patch is perfectly fine. Please see my question as half survey half
> commitment device. I don't think we have a crisp enough understanding
> of responsibilities of "corporate" maintainers. It always worries me
> when I see someone who never (AFAICT) sent an email to the list before
> get nominated as a maintainer.
>
> So I'd like to hear from Sathesh, clearly stated, what responsibilities
> and SLAs he's taking on. Once we gather input of this nature from a
> handful of maintainers maybe we can distill a guide in
> Documentation/process/...
Let me suggest one responsibility:
- reply to maintainers' questions in a timely manner...
Please repost with the answer folded into the commit message
once you figure out what to say.
--
pw-bot: cr
prev parent reply other threads:[~2023-06-20 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:10 [PATCH] MAINTAINERS: update email addresses of octeon_ep driver maintainers Sathesh Edara
2023-06-15 15:34 ` Veerasenareddy Burru
2023-06-15 17:13 ` Jakub Kicinski
2023-06-16 5:04 ` [EXT] " Veerasenareddy Burru
2023-06-16 17:12 ` Jakub Kicinski
2023-06-20 16:18 ` Jakub Kicinski [this message]
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=20230620091800.736bf269@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=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=vburru@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).