From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-10-03 (i40e, iavf)
Date: Wed, 4 Oct 2023 17:28:33 -0700 [thread overview]
Message-ID: <20231004172833.12033543@kernel.org> (raw)
In-Reply-To: <20231003223610.2004976-1-anthony.l.nguyen@intel.com>
On Tue, 3 Oct 2023 15:36:08 -0700 Tony Nguyen wrote:
> This series contains updates to i40e and iavf drivers.
>
> Yajun Deng aligns reporting of buffer exhaustion statistics to follow
> documentation for i40e.
>
> Jake removes undesired 'inline' from functions in iavf.
> ---
> v2:
> - Drop, previous patch 3, as a better solution [1] is upcoming [2]
Ah, here it is. Maybe it'd be safer not to change the title of
the cover letter for v2? Sooner or later it may trip some jet
lagged netdev maintainer if patchwork doesn't recognize v2
and auto-supersede v1 ;)
next prev parent reply other threads:[~2023-10-05 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 22:36 [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-10-03 (i40e, iavf) Tony Nguyen
2023-10-03 22:36 ` [PATCH net-next v2 1/2] i40e: Add rx_missed_errors for buffer exhaustion Tony Nguyen
2023-10-03 22:36 ` [PATCH net-next v2 2/2] iavf: remove "inline" functions from iavf_txrx.c Tony Nguyen
2023-10-05 0:28 ` Jakub Kicinski [this message]
2023-10-05 16:07 ` [PATCH net-next v2 0/2][pull request] Intel Wired LAN Driver Updates 2023-10-03 (i40e, iavf) Tony Nguyen
2023-10-05 0:30 ` 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=20231004172833.12033543@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).