From: "yangx.jy@fujitsu.com" <yangx.jy@fujitsu.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Olga Kornievskaia <aglo@umich.edu>,
Leon Romanovsky <leon@kernel.org>,
Bob Pearson <rpearsonhpe@gmail.com>,
Jason Gunthorpe <jgg@nvidia.com>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: RXE status in the upstream rping using rxe
Date: Fri, 20 Aug 2021 07:42:25 +0000 [thread overview]
Message-ID: <611F5CD8.2020504@fujitsu.com> (raw)
In-Reply-To: <CAD=hENeYiTrfxDTAS9UkF8tn7=wa49H0DQuCBKeHpd+L6qM4SQ@mail.gmail.com>
On 2021/8/20 11:31, Zhu Yanjun wrote:
> Latest kernel + latest rdma-coOnre< ------rping----> 5.10.y stable +
> latest rdma-core
> Latest kernel + latest rdma-core< ------rping----> 5.11.y stable +
> latest rdma-core
> Latest kernel + latest rdma-core< ------rping----> 5.12.y stable +
> latest rdma-core
> Latest kernel + latest rdma-core< ------rping----> 5.13.y stable +
> latest rdma-core
>
> The above works well.
Hi Yanjun,
Sorry, I don't know why you cannot reproduce the bug.
Did you see the similar bug reported by Olga Kornievskaia?
https://www.spinics.net/lists/linux-rdma/msg104358.html
https://www.spinics.net/lists/linux-rdma/msg104359.html
https://www.spinics.net/lists/linux-rdma/msg104360.html
Best Regards,
Xiao Yang
> Zhu Yanjun
>
next prev parent reply other threads:[~2021-08-20 7:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 18:07 RXE status in the upstream rping using rxe Leon Romanovsky
2021-08-04 1:01 ` Zhu Yanjun
2021-08-04 1:09 ` Zhu Yanjun
2021-08-04 5:41 ` Leon Romanovsky
2021-08-04 9:05 ` Zhu Yanjun
2021-08-06 2:37 ` Olga Kornievskaia
2021-08-17 2:28 ` Zhu Yanjun
2021-08-18 6:43 ` yangx.jy
2021-08-18 7:20 ` Zhu Yanjun
2021-08-18 7:44 ` yangx.jy
2021-08-18 8:28 ` Zhu Yanjun
2021-08-18 14:33 ` yangx.jy
2021-08-20 3:31 ` Zhu Yanjun
2021-08-20 7:42 ` yangx.jy [this message]
2021-08-20 21:40 ` Bob Pearson
2021-08-20 22:09 ` Bob Pearson
2021-08-13 21:53 ` Bob Pearson
2021-08-14 5:32 ` Leon Romanovsky
2021-08-23 7:53 ` Zhu Yanjun
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=611F5CD8.2020504@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=aglo@umich.edu \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.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.