From: patchwork-bot+netdevbpf@kernel.org
To: Shay Agroskin <shayagr@amazon.com>
Cc: 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,
gtzalik@amazon.com, netanel@amazon.com, alisaidi@amazon.com,
benh@amazon.com, akiyano@amazon.com, sameehj@amazon.com,
ndagan@amazon.com
Subject: Re: [PATCH V3 net 0/3] Fixes for ENA driver
Date: Wed, 25 Nov 2020 00:20:06 +0000 [thread overview]
Message-ID: <160626360618.17224.5751692742055805114.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201123190859.21298-1-shayagr@amazon.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Mon, 23 Nov 2020 21:08:56 +0200 you wrote:
> Hi all,
> This series fixes some issues in the ENA driver:
>
> - fix wrong data offset on machines that support rx offset
> - work-around Intel iommu issue
> - fix out of bound access when request id is wrong
>
> [...]
Here is the summary with links:
- [V3,net,1/3] net: ena: handle bad request id in ena_netdev
https://git.kernel.org/netdev/net/c/5b7022cf1dc0
- [V3,net,2/3] net: ena: set initial DMA width to avoid intel iommu issue
https://git.kernel.org/netdev/net/c/09323b3bca95
- [V3,net,3/3] net: ena: fix packet's addresses for rx_offset feature
https://git.kernel.org/netdev/net/c/1396d3148bd2
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:[~2020-11-25 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 19:08 [PATCH V3 net 0/3] Fixes for ENA driver Shay Agroskin
2020-11-23 19:08 ` [PATCH V3 net 1/3] net: ena: handle bad request id in ena_netdev Shay Agroskin
2020-11-23 19:08 ` [PATCH V3 net 2/3] net: ena: set initial DMA width to avoid intel iommu issue Shay Agroskin
2020-11-23 19:08 ` [PATCH V3 net 3/3] net: ena: fix packet's addresses for rx_offset feature Shay Agroskin
2020-11-25 0:20 ` 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=160626360618.17224.5751692742055805114.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=dwmw@amazon.com \
--cc=gtzalik@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=netdev@vger.kernel.org \
--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