From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<gakula@marvell.com>, <hkelam@marvell.com>,
<sgoutham@marvell.com>, <lcherian@marvell.com>,
<bbhushan2@marvell.com>, <jerinj@marvell.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net v2] octeontx2-af: Send Link events one by one
Date: Thu, 15 May 2025 17:34:26 +0000 [thread overview]
Message-ID: <aCYlosmI-28w80PJ@3958e7e617f8> (raw)
In-Reply-To: <20250515101937.72ae5ef9@kernel.org>
On 2025-05-15 at 17:19:37, Jakub Kicinski (kuba@kernel.org) wrote:
> On Thu, 15 May 2025 16:41:18 +0000 Subbaraya Sundeep wrote:
> > On 2025-05-15 at 14:12:39, Jakub Kicinski (kuba@kernel.org) wrote:
> > > On Wed, 14 May 2025 11:58:28 +0530 Subbaraya Sundeep wrote:
> > > > Send link events one after another otherwise new message
> > > > is overwriting the message which is being processed by PF.
> > >
> > > Please respond to reviewers in a timely fashion.
> >
> > Just want to know is it you or bot?
>
> Have you seen me reply with the same text to someone else?
> Oh, that's right, you don't read the list, how would you know..
>
:)
> > What is the time limit here?
> > Have to respond within 24hr?
>
> The review cadence on netdev is 24h.
Got it this patch missed your recent pull request because of my
delay in response.
Thanks,
Sundeep
prev parent reply other threads:[~2025-05-15 17:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 6:28 [PATCH net v2] octeontx2-af: Send Link events one by one Subbaraya Sundeep
2025-05-14 8:11 ` Michal Swiatkowski
2025-05-15 16:35 ` Subbaraya Sundeep
2025-05-15 14:12 ` Jakub Kicinski
2025-05-15 16:41 ` Subbaraya Sundeep
2025-05-15 17:19 ` Jakub Kicinski
2025-05-15 17:34 ` Subbaraya Sundeep [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=aCYlosmI-28w80PJ@3958e7e617f8 \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).