From: Leon Romanovsky <leon@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch, jgg@ziepe.ca,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
tatyana.e.nikolova@intel.com, david.m.ertman@intel.com,
przemyslaw.kitszel@intel.com
Subject: Re: [PATCH net-next,rdma-next v2 0/5][pull request] Prepare for Intel IPU E2000 (GEN3)
Date: Mon, 12 May 2025 14:05:11 +0300 [thread overview]
Message-ID: <20250512110511.GD22843@unreal> (raw)
In-Reply-To: <20250509200712.2911060-1-anthony.l.nguyen@intel.com>
On Fri, May 09, 2025 at 01:07:06PM -0700, Tony Nguyen wrote:
> This is the first part in introducing RDMA support for idpf.
> This shared pull request targets both net-next and rdma-next branches
> and is based on tag v6.15-rc1.
RDMA part look ok, nothing that can't be fixed later.
I'll wait till Jakub merge this series to netdev tree and will merge it too.
Thanks
next prev parent reply other threads:[~2025-05-12 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 20:07 [PATCH net-next,rdma-next v2 0/5][pull request] Prepare for Intel IPU E2000 (GEN3) Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 1/5] iidc/ice/irdma: Rename IDC header file Tony Nguyen
2025-05-13 2:20 ` patchwork-bot+netdevbpf
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 2/5] iidc/ice/irdma: Rename to iidc_* convention Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 3/5] iidc/ice/irdma: Break iidc.h into two headers Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 4/5] ice: Replace ice specific DSCP mapping num with a kernel define Tony Nguyen
2025-05-09 20:07 ` [PATCH net-next,rdma-next v2 5/5] iidc/ice/irdma: Update IDC to support multiple consumers Tony Nguyen
2025-05-12 11:05 ` Leon Romanovsky [this message]
2025-05-13 11:21 ` [PATCH net-next,rdma-next v2 0/5][pull request] Prepare for Intel IPU E2000 (GEN3) Leon Romanovsky
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=20250512110511.GD22843@unreal \
--to=leon@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tatyana.e.nikolova@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.