From: Jakub Kicinski <kuba@kernel.org>
To: Geetha sowjanya <gakula@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<davem@davemloft.net>, <pabeni@redhat.com>, <jiri@resnulli.us>,
<edumazet@google.com>, <sgoutham@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>
Subject: Re: [net-next PATCH v4 0/4] Refactoring RVU NIC driver
Date: Wed, 30 Oct 2024 17:52:20 -0700 [thread overview]
Message-ID: <20241030175220.0f2d5046@kernel.org> (raw)
In-Reply-To: <20241023161843.15543-1-gakula@marvell.com>
On Wed, 23 Oct 2024 21:48:39 +0530 Geetha sowjanya wrote:
> As suggested by "Jiri Pirko", submitting as separate patchset.
>
> v3-v4:
> (Suggested by "Jakub Kicinski").
These are our real names, you don't have to put them in quotes :)
While I'm typing - small nit for the future, please wrap the cover
letter at 72 chars, just like the commit messages.
next prev parent reply other threads:[~2024-10-31 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 16:18 [net-next PATCH v4 0/4] Refactoring RVU NIC driver Geetha sowjanya
2024-10-23 16:18 ` [net-next PATCH v4 1/4] octeontx2-pf: Define common API for HW resources configuration Geetha sowjanya
2024-10-24 15:03 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 2/4] octeontx2-pf: Add new APIs for queue memory alloc/free Geetha sowjanya
2024-10-24 15:02 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 3/4] octeontx2-pf: Reuse PF max mtu value Geetha sowjanya
2024-10-24 15:00 ` Simon Horman
2024-10-23 16:18 ` [net-next PATCH v4 4/4] octeontx2-pf: Move shared APIs to header file Geetha sowjanya
2024-10-24 15:00 ` Simon Horman
2024-10-31 0:52 ` Jakub Kicinski [this message]
2024-10-31 1:10 ` [net-next PATCH v4 0/4] Refactoring RVU NIC driver patchwork-bot+netdevbpf
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=20241030175220.0f2d5046@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@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).