public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
	Avihai Horon <avihaih@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	Mark Zhang <markzhang@nvidia.com>
Subject: [PATCH rdma-next v1 0/3] Skip holes in GID table
Date: Thu,  9 Dec 2021 15:16:04 +0200	[thread overview]
Message-ID: <cover.1639055490.git.leonro@nvidia.com> (raw)

From: Leon Romanovsky <leonro@nvidia.com>

Changelog:
v1:
 * Removed variable assignment in rdma_query_gid
 * Changed special error code handling of return value from
   rdma_query_gid to continue search.
v0: https://lore.kernel.org/all/cover.1637581778.git.leonro@nvidia.com

---------------------------------------------------------------------

Hi,

This short series extends rdma_query_gid() callers to skip holes
in GID tables.

Thanks

Avihai Horon (3):
  RDMA/core: Modify rdma_query_gid() to return accurate error codes
  RDMA/core: Let ib_find_gid() continue search even after empty entry
  RDMA/cma: Let cma_resolve_ib_dev() continue search even after empty
    entry

 drivers/infiniband/core/cache.c  | 12 +++++++++---
 drivers/infiniband/core/cma.c    | 12 +++++++++---
 drivers/infiniband/core/device.c |  3 ++-
 3 files changed, 20 insertions(+), 7 deletions(-)

-- 
2.33.1


             reply	other threads:[~2021-12-09 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 13:16 Leon Romanovsky [this message]
2021-12-09 13:16 ` [PATCH rdma-next v1 1/3] RDMA/core: Modify rdma_query_gid() to return accurate error codes Leon Romanovsky
2021-12-09 18:17   ` Leon Romanovsky
2021-12-09 13:16 ` [PATCH rdma-next v1 2/3] RDMA/core: Let ib_find_gid() continue search even after empty entry Leon Romanovsky
2021-12-09 13:16 ` [PATCH rdma-next v1 3/3] RDMA/cma: Let cma_resolve_ib_dev() " Leon Romanovsky
2021-12-15  0:12 ` [PATCH rdma-next v1 0/3] Skip holes in GID table Jason Gunthorpe

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=cover.1639055490.git.leonro@nvidia.com \
    --to=leon@kernel.org \
    --cc=avihaih@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@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