From: Jakub Kicinski <kuba@kernel.org>
To: Rushil Gupta <rushilg@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
pkaligineedi@google.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, willemb@google.com,
hramamurthy@google.com, Shailend Chand <shailend@google.com>,
Ziwei Xiao <ziweixiao@google.com>
Subject: Re: [PATCH net-next] gve: Add retry logic for recoverable adminq errors
Date: Mon, 1 Jul 2024 14:25:02 -0700 [thread overview]
Message-ID: <20240701142502.1a831c74@kernel.org> (raw)
In-Reply-To: <CANzqiF7TQW2yUM14XS68CxM35yJpq8DCRJRonMcyfTpfatBtMQ@mail.gmail.com>
On Sat, 29 Jun 2024 10:56:27 -0700 Rushil Gupta wrote:
> > Since Jeroen is a maintainer of this driver, and you are not listed
> > in the MAINTAINERS file I don't understand why you're the one sending
> > this. We can't teach everyone at google the upstream process one by
> > one so I'd like to request that only the listed maintainers post pure
> > GVE patches (or the folks who are heavily involved upstream).
>
> I could not find one single documentation that says only listed
> maintainers can post pure patches.
> Authors of some of the recently accepted patches were in fact not in
> the MAINTAINERS file.
It's not documented because we have to resort to it very rarely.
The escalation path is - remind of the process -> request that
someone knowledgeable reviews the code prior to posting -> limit
submitters.
> I am sending this patch as I was involved in getting this code to the
> upstream-ready state and testing it internally.
> However, if other GVE maintainers wish to follow this rule; I am ok
> with your suggestion.
prev parent reply other threads:[~2024-07-01 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 20:41 [PATCH net-next] gve: Add retry logic for recoverable adminq errors Rushil Gupta
2024-06-29 1:02 ` Jakub Kicinski
2024-06-29 17:56 ` Rushil Gupta
2024-07-01 21:25 ` 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=20240701142502.1a831c74@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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).