public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: Jinpu Wang <jinpu.wang@ionos.com>,
	"Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>
Cc: "haris.iqbal@ionos.com" <haris.iqbal@ionos.com>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"leon@kernel.org" <leon@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for-next v2 3/3] RDMA/rtrs: Fix rxe_dealloc_pd warning
Date: Tue, 25 Apr 2023 14:10:28 +0800	[thread overview]
Message-ID: <f353ba56-0c12-edad-0cd6-6c8bb01c6ddc@linux.dev> (raw)
In-Reply-To: <CAMGffE=M+DKumLvj=pyebxjDg3Ot+h5BGkcqxyJPiYu0C_6KHQ@mail.gmail.com>



On 4/24/23 12:33, Jinpu Wang wrote:
>>> Can we factor out a function for above? Then rtrs_clt_stop_and_destroy_conns
>>> might reuse it as well.
>> I'm open to this. but they are a bit difference IMHO.
> we can do the refactor later after bugfix.

Yes, maybe next cycle.

Thanks,
Guoqing

  reply	other threads:[~2023-04-25  6:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  1:26 [PATCH for-next v2 0/3] RDMA/rtrs: bugfix and cleanups Li Zhijian
2023-04-23  1:26 ` [PATCH for-next v2 1/3] RDMA/rtrs: remove duplicate cq_num assignment Li Zhijian
2023-04-23  1:26 ` [PATCH for-next v2 2/3] RDMA/rtrs: Fix the last iu->buf leak in err path Li Zhijian
2023-04-23  2:56   ` Guoqing Jiang
2023-04-24  5:18   ` Jinpu Wang
2023-04-23  1:26 ` [PATCH for-next v2 3/3] RDMA/rtrs: Fix rxe_dealloc_pd warning Li Zhijian
2023-04-23  3:08   ` Guoqing Jiang
2023-04-23  7:29     ` Zhijian Li (Fujitsu)
2023-04-24  4:33       ` Jinpu Wang
2023-04-25  6:10         ` Guoqing Jiang [this message]
2023-04-24  4:32   ` Jinpu Wang
2023-04-25  1:03 ` [PATCH for-next v2 0/3] RDMA/rtrs: bugfix and cleanups Zhijian Li (Fujitsu)

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=f353ba56-0c12-edad-0cd6-6c8bb01c6ddc@linux.dev \
    --to=guoqing.jiang@linux.dev \
    --cc=haris.iqbal@ionos.com \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lizhijian@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