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
Subject: Re: (subset) [PATCH for-next 0/9] RDMA/hns: Bugfixes and one improvement
Date: Tue, 10 Sep 2024 16:13:43 +0300 [thread overview]
Message-ID: <172597402310.3387045.13638568220298079896.b4-ty@kernel.org> (raw)
In-Reply-To: <20240906093444.3571619-1-huangjunxian6@hisilicon.com>
On Fri, 06 Sep 2024 17:34:35 +0800, Junxian Huang wrote:
> This is a series of hns patches. Patch #8 is an improvement for
> hem allocation performance, and the others are some fixes.
>
> Chengchang Tang (2):
> RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled
> RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS
>
> [...]
Applied, thanks!
[1/9] RDMA/hns: Don't modify rq next block addr in HIP09 QPC
https://git.kernel.org/rdma/rdma/c/6928d264e328e0
[2/9] RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08
https://git.kernel.org/rdma/rdma/c/fd8489294dd2be
[4/9] RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range()
https://git.kernel.org/rdma/rdma/c/d586628b169d14
[5/9] RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled
https://git.kernel.org/rdma/rdma/c/74d315b5af1802
[6/9] RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler
https://git.kernel.org/rdma/rdma/c/4321feefa5501a
[7/9] RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS
https://git.kernel.org/rdma/rdma/c/ce196f6297c7f3
[8/9] RDMA/hns: Optimize hem allocation performance
https://git.kernel.org/rdma/rdma/c/fe51f6254d81f5
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2024-09-10 13:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 9:34 [PATCH for-next 0/9] RDMA/hns: Bugfixes and one improvement Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 1/9] RDMA/hns: Don't modify rq next block addr in HIP09 QPC Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 2/9] RDMA/hns: Fix Use-After-Free of rsv_qp on HIP08 Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 3/9] RDMA/hns: Fix cpu stuck caused by printings during reset Junxian Huang
2024-09-10 13:09 ` Leon Romanovsky
2024-09-11 1:34 ` Junxian Huang
2024-09-11 13:25 ` Leon Romanovsky
2024-09-12 1:04 ` Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 4/9] RDMA/hns: Fix the overflow risk of hem_list_calc_ba_range() Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 5/9] RDMA/hns: Fix spin_unlock_irqrestore() called with IRQs enabled Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 6/9] RDMA/hns: Fix VF triggering PF reset in abnormal interrupt handler Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 7/9] RDMA/hns: Fix 1bit-ECC recovery address in non-4K OS Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 8/9] RDMA/hns: Optimize hem allocation performance Junxian Huang
2024-09-06 9:34 ` [PATCH for-next 9/9] RDMA/hns: Fix different dgids mapping to the same dip_idx Junxian Huang
2024-09-10 13:12 ` Leon Romanovsky
2024-10-17 13:21 ` Junxian Huang
2024-10-29 12:40 ` Leon Romanovsky
2024-09-10 13:13 ` [PATCH for-next 0/9] RDMA/hns: Bugfixes and one improvement Leon Romanovsky
2024-09-10 13:13 ` 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=172597402310.3387045.13638568220298079896.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 \
/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