From: patchwork-bot+netdevbpf@kernel.org
To: Shai Malin <smalin@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-nvme@lists.infradead.org, sagi@grimberg.me, hch@lst.de,
axboe@fb.com, kbusch@kernel.org, aelior@marvell.com,
mkalderon@marvell.com, okulkarni@marvell.com,
pkushwaha@marvell.com, prabhakar.pkin@gmail.com,
malin1024@gmail.com
Subject: Re: [PATCH 0/7] QED NVMeTCP Offload
Date: Thu, 03 Jun 2021 21:10:05 +0000 [thread overview]
Message-ID: <162275460557.4513.1472731666027007171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210602171655.23581-1-smalin@marvell.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Jun 2021 20:16:48 +0300 you wrote:
> Hi Dave,
>
> Intro:
> ======
> This is the qed part of Marvell’s NVMeTCP offload series, shared as
> RFC series "NVMeTCP Offload ULP and QEDN Device Drive".
> This part is a standalone series, and is not dependent on other parts
> of the RFC.
> The overall goal is to add qedn as the offload driver for NVMeTCP,
> alongside the existing offload drivers (qedr, qedi and qedf for rdma,
> iscsi and fcoe respectively).
>
> [...]
Here is the summary with links:
- [1/7] qed: Add TCP_ULP FW resource layout
https://git.kernel.org/netdev/net-next/c/1bd4f5716fc3
- [2/7] qed: Add NVMeTCP Offload PF Level FW and HW HSI
https://git.kernel.org/netdev/net-next/c/897e87a10c35
- [3/7] qed: Add NVMeTCP Offload Connection Level FW and HW HSI
https://git.kernel.org/netdev/net-next/c/76684ab8f4f9
- [4/7] qed: Add support of HW filter block
https://git.kernel.org/netdev/net-next/c/203d136e8958
- [5/7] qed: Add NVMeTCP Offload IO Level FW and HW HSI
https://git.kernel.org/netdev/net-next/c/ab47bdfd2e2e
- [6/7] qed: Add NVMeTCP Offload IO Level FW Initializations
https://git.kernel.org/netdev/net-next/c/826da4861430
- [7/7] qed: Add IP services APIs support
https://git.kernel.org/netdev/net-next/c/806ee7f81a2b
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:[~2021-06-03 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 17:16 [PATCH 0/7] QED NVMeTCP Offload Shai Malin
2021-06-02 17:16 ` [PATCH 1/7] qed: Add TCP_ULP FW resource layout Shai Malin
2021-06-02 17:16 ` [PATCH 2/7] qed: Add NVMeTCP Offload PF Level FW and HW HSI Shai Malin
2021-06-02 17:16 ` [PATCH 3/7] qed: Add NVMeTCP Offload Connection " Shai Malin
2021-06-02 17:16 ` [PATCH 4/7] qed: Add support of HW filter block Shai Malin
2021-06-02 17:16 ` [PATCH 5/7] qed: Add NVMeTCP Offload IO Level FW and HW HSI Shai Malin
2021-06-02 17:16 ` [PATCH 6/7] qed: Add NVMeTCP Offload IO Level FW Initializations Shai Malin
2021-06-02 17:16 ` [PATCH 7/7] qed: Add IP services APIs support Shai Malin
2021-06-03 21:10 ` 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=162275460557.4513.1472731666027007171.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aelior@marvell.com \
--cc=axboe@fb.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mkalderon@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=okulkarni@marvell.com \
--cc=pkushwaha@marvell.com \
--cc=prabhakar.pkin@gmail.com \
--cc=sagi@grimberg.me \
--cc=smalin@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).