public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>
Subject: Re: [PATCH] RDMA/rxe: Remove the member 'type' of struct rxe_mr
Date: Mon, 24 Oct 2022 20:08:21 +0300	[thread overview]
Message-ID: <Y1bGhcbwBWYrfrsD@unreal> (raw)
In-Reply-To: <be29ec7e-9f9e-40a1-358f-4a44c5defc0c@gmail.com>

On Mon, Oct 24, 2022 at 09:07:11AM -0500, Bob Pearson wrote:
> On 10/24/22 06:51, Leon Romanovsky wrote:
> > On Fri, Oct 21, 2022 at 01:45:17PM +0000, yangx.jy@fujitsu.com wrote:
> >> The member 'type' is included in both struct rxe_mr and struct ib_mr
> >> so remove the duplicate one of struct rxe_mr.
> >>
> >> Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
> >> ---
> >>  drivers/infiniband/sw/rxe/rxe_mr.c    | 16 ++++++++--------
> >>  drivers/infiniband/sw/rxe/rxe_verbs.h |  1 -
> >>  2 files changed, 8 insertions(+), 9 deletions(-)
> > 
> > <...>
> > 
> >>  	default:
> >>  		pr_warn("%s: mr type (%d) not supported\n",
> >> -			__func__, mr->type);
> >> +			__func__, mr->ibmr.type);
> >>  		return -EFAULT;
> > 
> > <...>
> > 
> >> -	if (unlikely(mr->type != IB_MR_TYPE_MEM_REG)) {
> >> -		pr_warn("%s: mr->type (%d) is wrong type\n", __func__, mr->type);
> >> +	if (unlikely(mr->ibmr.type != IB_MR_TYPE_MEM_REG)) {
> >> +		pr_warn("%s: mr type (%d) is wrong\n", __func__, mr->ibmr.type);
> > 
> > Someone needs to convert pr_*() calls to ibdev_*() prints.
> > 
> > Thanks
> 
> I have a patch laying around that does this. Hoping some of the backlog of rxe patches gets
> accepted so I don't have to backport everything.

The way to move forward with RXE patches is to collect Reviewed-by from
other active RXE contributors.

I'm not taking RXE patches without ROB, that don't apply cleanly and which
don't follow kernel coding style both in code and in commit messages.

Thanks

> 
> Bob

  reply	other threads:[~2022-10-24 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 13:45 [PATCH] RDMA/rxe: Remove the member 'type' of struct rxe_mr yangx.jy
2022-10-23 17:18 ` Bob Pearson
2022-10-24 11:51 ` Leon Romanovsky
2022-10-24 14:07   ` Bob Pearson
2022-10-24 17:08     ` Leon Romanovsky [this message]
2022-10-24 11:57 ` Leon Romanovsky
2022-10-27  6:34   ` Yang, Xiao/杨 晓

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=Y1bGhcbwBWYrfrsD@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearsonhpe@gmail.com \
    --cc=yangx.jy@fujitsu.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