mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, Junxian Huang <huangjunxian6@hisilicon.com>
Cc: linux-rdma@vger.kernel.org, linuxarm@huawei.com,
	 linux-kernel@vger.kernel.org, tangchengchang@huawei.com
Subject: Re: [PATCH for-rc 0/4] RDMA/hns: Bugfixes
Date: Mon, 23 Dec 2024 09:58:47 -0500	[thread overview]
Message-ID: <173496592736.403699.6324840157920941971.b4-ty@kernel.org> (raw)
In-Reply-To: <20241220055249.146943-1-huangjunxian6@hisilicon.com>


On Fri, 20 Dec 2024 13:52:45 +0800, Junxian Huang wrote:
> Here are some recent bugfixes for hns.
> 
> Chengchang Tang (3):
>   RDMA/hns: Fix accessing invalid dip_ctx during destroying QP
>   RDMA/hns: Fix warning storm caused by invalid input in IO path
>   RDMA/hns: Fix missing flush CQE for DWQE
> 
> [...]

Applied, thanks!

[1/4] RDMA/hns: Fix mapping error of zero-hop WQE buffer
      https://git.kernel.org/rdma/rdma/c/8673a6c2d9e483
[2/4] RDMA/hns: Fix accessing invalid dip_ctx during destroying QP
      https://git.kernel.org/rdma/rdma/c/0572eccf239ce4
[3/4] RDMA/hns: Fix warning storm caused by invalid input in IO path
      https://git.kernel.org/rdma/rdma/c/fa5c4ba8cdbfd2
[4/4] RDMA/hns: Fix missing flush CQE for DWQE
      https://git.kernel.org/rdma/rdma/c/e3debdd48423d3

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


      parent reply	other threads:[~2024-12-23 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20  5:52 Junxian Huang
2024-12-20  5:52 ` [PATCH for-rc 1/4] RDMA/hns: Fix mapping error of zero-hop WQE buffer Junxian Huang
2024-12-20  5:52 ` [PATCH for-rc 2/4] RDMA/hns: Fix accessing invalid dip_ctx during destroying QP Junxian Huang
2024-12-20  5:52 ` [PATCH for-rc 3/4] RDMA/hns: Fix warning storm caused by invalid input in IO path Junxian Huang
2024-12-20  5:52 ` [PATCH for-rc 4/4] RDMA/hns: Fix missing flush CQE for DWQE Junxian Huang
2024-12-23 14:58 ` Leon Romanovsky [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=173496592736.403699.6324840157920941971.b4-ty@kernel.org \
    --to=leon@kernel.org \
    --cc=huangjunxian6@hisilicon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=tangchengchang@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

all inboxes | Powered by JetHome®