All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Weihang Li <liweihang@huawei.com>
Cc: <dledford@redhat.com>, <leon@kernel.org>,
	<linux-rdma@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH v2 for-next] RDMA/hns: Refactor the hns_roce_buf allocation flow
Date: Mon, 23 Nov 2020 19:41:00 -0400	[thread overview]
Message-ID: <20201123234100.GA142513@nvidia.com> (raw)
In-Reply-To: <1605347916-15964-1-git-send-email-liweihang@huawei.com>

On Sat, Nov 14, 2020 at 05:58:36PM +0800, Weihang Li wrote:
> From: Xi Wang <wangxi11@huawei.com>
> 
> Add a group of flags to control the 'struct hns_roce_buf' allocation
> flow, this is used to support the caller running in atomic context.
> 
> Signed-off-by: Xi Wang <wangxi11@huawei.com>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> Changes since v1:
> - Fix issues about WARN_ON() and IS_ERR_OR_NULL().
> Link: https://patchwork.kernel.org/project/linux-rdma/patch/1603967462-18124-1-git-send-email-liweihang@huawei.com/
> 
>  drivers/infiniband/hw/hns/hns_roce_alloc.c  | 128 ++++++++++++++++------------
>  drivers/infiniband/hw/hns/hns_roce_device.h |  51 +++++------
>  drivers/infiniband/hw/hns/hns_roce_mr.c     |  39 +++------
>  3 files changed, 113 insertions(+), 105 deletions(-)

Applied to for-next, thanks

Jason

      reply	other threads:[~2020-11-23 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  9:58 [PATCH v2 for-next] RDMA/hns: Refactor the hns_roce_buf allocation flow Weihang Li
2020-11-23 23:41 ` Jason Gunthorpe [this message]

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=20201123234100.GA142513@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liweihang@huawei.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 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.