Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Md Haris Iqbal <haris.iqbal@ionos.com>
Cc: linux-rdma@vger.kernel.org, jgg@ziepe.ca, jinpu.wang@ionos.com
Subject: Re: [PATCH for-next 0/3] Use the right sg_cnt after ib_dma_map_sg
Date: Sun, 21 Aug 2022 12:27:11 +0300	[thread overview]
Message-ID: <YwH6b32Bsw08A70T@unreal> (raw)
In-Reply-To: <20220818105355.110344-1-haris.iqbal@ionos.com>

On Thu, Aug 18, 2022 at 12:53:52PM +0200, Md Haris Iqbal wrote:
> Hi Jason, hi Leon,
> 
> Please consider to include following changes to the next merge window.
> 
> The patchset is organized as follows:
> 1: Add output for debug purposes
> 2: Use correct count returned form ib_dma_map_sg for rtrs-clt
> 3: Use correct count returned form ib_dma_map_sg for rtrs-srv
> 
> Jack Wang (3):
>   RDMA/rtrs-clt: Output sg index when warning on

Applied to -next.

>   RDMA/rtrs-clt: Use the right sg_cnt after ib_dma_map_sg
>   RDMA/rtrs-srv: Pass the correct number of entries for dma mapped SGL

Applied to -rc.

> 
>  drivers/infiniband/ulp/rtrs/rtrs-clt.c |  9 +++++----
>  drivers/infiniband/ulp/rtrs/rtrs-srv.c | 14 +++++++-------
>  drivers/infiniband/ulp/rtrs/rtrs.c     |  2 +-
>  3 files changed, 13 insertions(+), 12 deletions(-)
> 
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2022-08-21  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 10:53 [PATCH for-next 0/3] Use the right sg_cnt after ib_dma_map_sg Md Haris Iqbal
2022-08-18 10:53 ` [PATCH for-next 1/3] RDMA/rtrs-clt: Output sg index when warning on Md Haris Iqbal
2022-08-18 10:53 ` [PATCH for-next 2/3] RDMA/rtrs-clt: Use the right sg_cnt after ib_dma_map_sg Md Haris Iqbal
2022-08-18 10:53 ` [PATCH for-next 3/3] RDMA/rtrs-srv: Pass the correct number of entries for dma mapped SGL Md Haris Iqbal
2022-08-21  9:27 ` 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=YwH6b32Bsw08A70T@unreal \
    --to=leon@kernel.org \
    --cc=haris.iqbal@ionos.com \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --cc=linux-rdma@vger.kernel.org \
    /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