public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-rc 0/3] RDMA/hns: Bugfix and improvements
Date: Thu, 1 Jun 2023 20:00:46 -0300	[thread overview]
Message-ID: <ZHkjHl1H02sr8pnq@nvidia.com> (raw)
In-Reply-To: <20230523121641.3132102-1-huangjunxian6@hisilicon.com>

On Tue, May 23, 2023 at 08:16:38PM +0800, Junxian Huang wrote:
> 1. #1-#2: The first two patches improves diagnostic information to
>    the driver.
> 
> 2. #3: The third patch removes unnecessary QP type checks.
> 
> 
> Chengchang Tang (2):
>   RDMA/hns: Fix hns_roce_table_get return value
>   RDMA/hns: Add clear_hem return value to log
> 
> Junxian Huang (1):
>   RDMA/hns: Remove unnecessary QP type checks

These are not -rc patches, they don't fix user facing things, so I put
them in for-next

Also there was a compile warning I fixed

../drivers/infiniband/hw/hns/hns_roce_hw_v2.c:767:20: warning: unused variable 'ibdev' [-Wunused-variable]
        struct ib_device *ibdev = &hr_dev->ib_dev;

Although it could probably use more fixing.

Jason

  parent reply	other threads:[~2023-06-01 23:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 12:16 [PATCH for-rc 0/3] RDMA/hns: Bugfix and improvements Junxian Huang
2023-05-23 12:16 ` [PATCH for-rc 1/3] RDMA/hns: Remove unnecessary QP type checks Junxian Huang
2023-05-23 12:16 ` [PATCH for-rc 2/3] RDMA/hns: Fix hns_roce_table_get return value Junxian Huang
2023-05-23 12:16 ` [PATCH for-rc 3/3] RDMA/hns: Add clear_hem return value to log Junxian Huang
2023-06-01 23:00 ` Jason Gunthorpe [this message]
2023-06-02  7:55   ` [PATCH for-rc 0/3] RDMA/hns: Bugfix and improvements Junxian Huang

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=ZHkjHl1H02sr8pnq@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=huangjunxian6@hisilicon.com \
    --cc=leon@kernel.org \
    --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