From: patchwork-bot+netdevbpf@kernel.org
To: Arinzon@ci.codeaurora.org, David <darinzon@amazon.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
dwmw@amazon.com, zorik@amazon.com, matua@amazon.com,
saeedb@amazon.com, msw@amazon.com, aliguori@amazon.com,
nafea@amazon.com, netanel@amazon.com, alisaidi@amazon.com,
benh@amazon.com, akiyano@amazon.com, ndagan@amazon.com,
shayagr@amazon.com, itzko@amazon.com, osamaabb@amazon.com,
evostrov@amazon.com, ofirt@amazon.com, netanel@annapurnalabs.com,
sameehj@amazon.com
Subject: Re: [PATCH v1 net 0/4] ENA driver bug fixes
Date: Thu, 11 Apr 2024 09:40:29 +0000 [thread overview]
Message-ID: <171282842954.17841.557508586983776545.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240410091358.16289-1-darinzon@amazon.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 10 Apr 2024 09:13:54 +0000 you wrote:
> From: David Arinzon <darinzon@amazon.com>
>
> This patchset contains multiple bug fixes for the
> ENA driver.
>
> David Arinzon (4):
> net: ena: Fix potential sign extension issue
> net: ena: Wrong missing IO completions check order
> net: ena: Fix incorrect descriptor free behavior
> net: ena: Set tx_info->xdpf value to NULL
>
> [...]
Here is the summary with links:
- [v1,net,1/4] net: ena: Fix potential sign extension issue
https://git.kernel.org/netdev/net/c/713a85195aad
- [v1,net,2/4] net: ena: Wrong missing IO completions check order
https://git.kernel.org/netdev/net/c/f7e417180665
- [v1,net,3/4] net: ena: Fix incorrect descriptor free behavior
https://git.kernel.org/netdev/net/c/bf02d9fe0063
- [v1,net,4/4] net: ena: Set tx_info->xdpf value to NULL
https://git.kernel.org/netdev/net/c/36a1ca01f045
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-11 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 9:13 [PATCH v1 net 0/4] ENA driver bug fixes darinzon
2024-04-10 9:13 ` [PATCH v1 net 1/4] net: ena: Fix potential sign extension issue darinzon
2024-04-10 21:49 ` Nelson, Shannon
2024-04-10 9:13 ` [PATCH v1 net 2/4] net: ena: Wrong missing IO completions check order darinzon
2024-04-10 21:51 ` Nelson, Shannon
2024-04-10 9:13 ` [PATCH v1 net 3/4] net: ena: Fix incorrect descriptor free behavior darinzon
2024-04-10 21:52 ` Nelson, Shannon
2024-04-10 9:13 ` [PATCH v1 net 4/4] net: ena: Set tx_info->xdpf value to NULL darinzon
2024-04-10 21:53 ` Nelson, Shannon
2024-04-11 9:40 ` patchwork-bot+netdevbpf [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=171282842954.17841.557508586983776545.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Arinzon@ci.codeaurora.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=evostrov@amazon.com \
--cc=itzko@amazon.com \
--cc=kuba@kernel.org \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netanel@annapurnalabs.com \
--cc=netdev@vger.kernel.org \
--cc=ofirt@amazon.com \
--cc=osamaabb@amazon.com \
--cc=saeedb@amazon.com \
--cc=sameehj@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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).