All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: Zhu Yanjun <yanjun.zhu@intel.com>,
	mustafa.ismail@intel.com, shiraz.saleem@intel.com, jgg@ziepe.ca,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCHv3 for-next 0/4] RDMA/irdma: Refactor irdma_reg_user_mr function
Date: Thu, 26 Jan 2023 12:59:35 +0200	[thread overview]
Message-ID: <Y9JdF5b+dzIchpOg@unreal> (raw)
In-Reply-To: <e59c54bf-03f7-2e27-2162-91dc3f896123@linux.dev>

On Thu, Jan 26, 2023 at 09:16:05AM +0800, Zhu Yanjun wrote:
> 在 2023/1/17 3:34, Zhu Yanjun 写道:
> > V2->V3: 1) Use netdev reverse Christmas tree rule;
> > 	2) Return 0 instead of err;
> > 	3) Remove unnecessary brackets;
> > 	4) Add an error label in error handler;
> > 	5) Initialize the structured variables;
> 
> Hi, Leon
> 
> Follow your advice, I made this patches.
> Please check it.

Everything is applied, sorry for the delay.

Thanks

  reply	other threads:[~2023-01-26 10:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 19:34 [PATCHv3 for-next 0/4] RDMA/irdma: Refactor irdma_reg_user_mr function Zhu Yanjun
2023-01-16 19:34 ` [PATCHv3 for-next 1/4] RDMA/irdma: Split MEM handler into irdma_reg_user_mr_type_mem Zhu Yanjun
2023-01-16 19:35 ` [PATCHv3 for-next 2/4] RDMA/irdma: Split mr alloc and free into new functions Zhu Yanjun
2023-01-16 19:35 ` [PATCHv3 for-next 3/4] RDMA/irdma: Split QP handler into irdma_reg_user_mr_type_qp Zhu Yanjun
2023-01-16 19:35 ` [PATCHv3 for-next 4/4] RDMA/irdma: Split CQ handler into irdma_reg_user_mr_type_cq Zhu Yanjun
2023-01-26  1:16 ` [PATCHv3 for-next 0/4] RDMA/irdma: Refactor irdma_reg_user_mr function Zhu Yanjun
2023-01-26 10:59   ` Leon Romanovsky [this message]
2023-01-26 13:40     ` Zhu Yanjun
2023-01-26 10:59 ` 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=Y9JdF5b+dzIchpOg@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mustafa.ismail@intel.com \
    --cc=shiraz.saleem@intel.com \
    --cc=yanjun.zhu@intel.com \
    --cc=yanjun.zhu@linux.dev \
    /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.