From: Honggang LI <honggangli@163.com>
To: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>
Cc: "zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RDMA/rxe: Fix kernel panic for fast registered MR
Date: Fri, 11 Apr 2025 15:56:51 +0800 [thread overview]
Message-ID: <Z_jLQ0c6t2LigbFJ@fedora> (raw)
In-Reply-To: <OS3PR01MB98657E6B788DBC4B11115102E5B62@OS3PR01MB9865.jpnprd01.prod.outlook.com>
On Fri, Apr 11, 2025 at 07:31:51AM +0000, Daisuke Matsuda (Fujitsu) wrote:
> However, this issue is already addressed in the for-rc tree.
> Cf. https://lore.kernel.org/linux-rdma/f845e90c-50ff-4e0f-9b73-55a704ba934f@linux.dev/T/#t
Yes, you are right. Please drop this patch.
prev parent reply other threads:[~2025-04-11 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 7:11 [PATCH] RDMA/rxe: Fix kernel panic for fast registered MR Honggang LI
2025-04-11 7:31 ` Daisuke Matsuda (Fujitsu)
2025-04-11 7:56 ` Honggang LI [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=Z_jLQ0c6t2LigbFJ@fedora \
--to=honggangli@163.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=zyjzyj2000@gmail.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.