All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jack Wang <jinpu.wang@ionos.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] RDMA: dma-mapping: Return an unsigned int from ib_dma_map_sg{,_attrs}
Date: Sun, 28 Aug 2022 14:09:47 +0300	[thread overview]
Message-ID: <YwtM+/nB1F6p1Ey3@unreal> (raw)
In-Reply-To: <20220826095615.74328-3-jinpu.wang@ionos.com>

On Fri, Aug 26, 2022 at 11:56:15AM +0200, Jack Wang wrote:
> Following 2a047e0662ae ("dma-mapping: return an unsigned int from dma_map_sg{,_attrs}")
> change the return value of ib_dma_map_sg{,attrs} to unsigned int.
> 
> Cc: Jason Gunthorpe <jgg@ziepe.ca>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: linux-rdma@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> 
> Signed-off-by: Jack Wang <jinpu.wang@ionos.com>
> ---
>  drivers/infiniband/core/device.c | 2 +-
>  include/rdma/ib_verbs.h          | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)

You forgot to change ib_dma_map_sgtable_attrs() and various
ib_dma_map_sg*() callers.

Thanks

  reply	other threads:[~2022-08-28 11:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  9:56 [PATCH 0/2] infiniband: Fxi dma_map_sg error check Jack Wang
2022-08-26  9:56 ` [PATCH 1/2] infiniband/mthca: Fix " Jack Wang
2022-08-28 10:10   ` Leon Romanovsky
2022-08-29  5:27     ` Jinpu Wang
2022-08-26  9:56 ` [PATCH 2/2] RDMA: dma-mapping: Return an unsigned int from ib_dma_map_sg{,_attrs} Jack Wang
2022-08-28 11:09   ` Leon Romanovsky [this message]
2022-08-29  9:40     ` Jinpu Wang
2022-08-29 12:06       ` Leon Romanovsky
2022-08-29 13:19         ` Jinpu Wang
2022-08-30  8:01           ` Leon Romanovsky
2022-08-30  8:23             ` Jinpu Wang
2022-08-30  9:13               ` 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=YwtM+/nB1F6p1Ey3@unreal \
    --to=leon@kernel.org \
    --cc=hch@lst.de \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.