mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	Mark Bloch <mbloch@nvidia.com>,
	Michael Guralnik <michaelgur@nvidia.com>,
	netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	Saeed Mahameed <saeedm@nvidia.com>, Shun Hao <shunh@nvidia.com>,
	Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH mlx5-next v1 0/5] Expose c0 and SW encap ICM for RDMA
Date: Tue, 12 Dec 2023 09:09:21 +0200	[thread overview]
Message-ID: <170236496138.251016.9253831188442382874.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1701871118.git.leon@kernel.org>


On Wed, 06 Dec 2023 16:01:33 +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Changelog:
> v1:
>  * Reordered patches
> v0: https://lore.kernel.org/all/cover.1701172481.git.leon@kernel.org
> 
> [...]

Applied, thanks!

[1/5] net/mlx5: Introduce indirect-sw-encap ICM properties
      https://git.kernel.org/rdma/rdma/c/1ca51628e73037
[2/5] RDMA/mlx5: Support handling of SW encap ICM area
      https://git.kernel.org/rdma/rdma/c/a429ec96c07f30
[3/5] net/mlx5: Manage ICM type of SW encap
      https://git.kernel.org/rdma/rdma/c/abf8e8f29a3cb6
[4/5] net/mlx5: E-Switch, expose eswitch manager vport
      https://git.kernel.org/rdma/rdma/c/eb524d0fd46249
[5/5] RDMA/mlx5: Expose register c0 for RDMA device
      https://git.kernel.org/rdma/rdma/c/d727d27db536fa

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>

      reply	other threads:[~2023-12-12  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 14:01 Leon Romanovsky
2023-12-12  7:09 ` Leon Romanovsky [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=170236496138.251016.9253831188442382874.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=edumazet@google.com \
    --cc=jgg@ziepe.ca \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=michaelgur@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=shunh@nvidia.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

all inboxes | Powered by JetHome®