From: Leon Romanovsky <leon@kernel.org>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 for-rc 0/2] RDMA/hns: Improvements for function resource configuration
Date: Mon, 24 Jul 2023 11:48:16 +0300 [thread overview]
Message-ID: <20230724084816.GA9776@unreal> (raw)
In-Reply-To: <20230721025146.450831-1-huangjunxian6@hisilicon.com>
On Fri, Jul 21, 2023 at 10:51:44AM +0800, Junxian Huang wrote:
> Here are 3 patches involving function resource configuration.
>
> 1. #1: The first patch supports getting xrcd num from firmware.
>
> 2. #2: The second patch removes a redundant configuration in driver,
> which is now handled by firmware.
>
> V2 removes 'inline' before function names in the third patch.
>
> V3 removes the third patch in V1 and V2.
>
> *** BLURB HERE ***
>
> Junxian Huang (1):
> RDMA/hns: Remove VF extend configuration
>
> Luoyouming (1):
> RDMA/hns: support get xrcd num from firmware
>
> drivers/infiniband/hw/hns/hns_roce_device.h | 1 -
> drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 89 +++------------------
> drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 13 +--
> 3 files changed, 14 insertions(+), 89 deletions(-)
Applied to -next.
Thanks
>
> --
> 2.30.0
>
next prev parent reply other threads:[~2023-07-24 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 2:51 [PATCH v3 for-rc 0/2] RDMA/hns: Improvements for function resource configuration Junxian Huang
2023-07-21 2:51 ` [PATCH v3 for-rc 1/2] RDMA/hns: support get xrcd num from firmware Junxian Huang
2023-07-21 2:51 ` [PATCH v3 for-rc 2/2] RDMA/hns: Remove VF extend configuration Junxian Huang
2023-07-24 8:48 ` Leon Romanovsky [this message]
2023-07-24 8:56 ` [PATCH v3 for-rc 0/2] RDMA/hns: Improvements for function resource configuration 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=20230724084816.GA9776@unreal \
--to=leon@kernel.org \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox