Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
	"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
	"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Subject: Re: [RESEND PATCH] RDMA/rxe: Remove unused qp parameter
Date: Mon, 18 Jul 2022 15:16:16 +0300	[thread overview]
Message-ID: <YtVPEFHs5VaLe+mY@unreal> (raw)
In-Reply-To: <4bca5022-2db6-b788-9a88-0615d6ea9e97@fujitsu.com>

On Mon, Jul 18, 2022 at 08:58:32AM +0000, yangx.jy@fujitsu.com wrote:
> On 2022/7/18 16:26, Leon Romanovsky wrote:
> > On Fri, Jul 08, 2022 at 03:55:50AM +0000, yangx.jy@fujitsu.com wrote:
> >> The qp parameter in free_rd_atomic_resource() has become
> >> unused so remove it directly.
> >>
> >> Fixes: 15ae1375ea91 ("RDMA/rxe: Fix qp reference counting for atomic ops")
> >> Signed-off-by: Xiao Yang <yangx.jy@fujitsu.com>
> >> ---
> >>   drivers/infiniband/sw/rxe/rxe_loc.h  | 2 +-
> >>   drivers/infiniband/sw/rxe/rxe_qp.c   | 6 +++---
> >>   drivers/infiniband/sw/rxe/rxe_resp.c | 2 +-
> >>   3 files changed, 5 insertions(+), 5 deletions(-)
> > 
> > The patch doesn't apply.
> > 
> > Thanks
> 
> Hi Leon,
> 
> Could you tell me why it doesn't apply?

Please, try to apply the patch to wip/leon-for-next branch.

Thanks

> 
> Best Regards,
> Xiao Yang

  reply	other threads:[~2022-07-18 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  3:55 [RESEND PATCH] RDMA/rxe: Remove unused qp parameter yangx.jy
2022-07-18  8:26 ` Leon Romanovsky
2022-07-18  8:58   ` yangx.jy
2022-07-18 12:16     ` Leon Romanovsky [this message]
2022-07-19  2:22       ` yangx.jy
2022-07-19  8:32         ` Leon Romanovsky
     [not found] <20220708013934.5022-1-yangx.jy@fujitsu.com>
2022-07-08  1:59 ` yangx.jy
2022-07-08  3:54   ` yangx.jy
2022-07-14 16:24     ` Bob Pearson

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