From: Bart Van Assche <bvanassche@acm.org>
To: Bob Pearson <rpearsonhpe@gmail.com>,
Yanjun Zhu <yanjun.zhu@linux.dev>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Bernard Metzler <bmt@zurich.ibm.com>
Subject: Re: Apparent regression in blktests since 5.18-rc1+
Date: Thu, 12 May 2022 15:25:16 -0700 [thread overview]
Message-ID: <529dbb0a-0b75-9752-62a3-a1235565aa1a@acm.org> (raw)
In-Reply-To: <b2908c39-636a-1cba-db22-838640385d84@gmail.com>
On 5/12/22 14:57, Bob Pearson wrote:
> I am trying to reproduce your result. What version of Linus' tree did you use?
> rdma for-next is 5.18-rc1+
> rdma for-rc is 5.18-rc6 (as of earlier today) which is an official tag. Not sure if there is an advanced one from that.
Hi Bob,
That must have been one of the most recent versions at the time I wrote
my email. Does the exact version matter? The test results I reported
should be identical for Linus' latest master branch.
Thanks,
Bart.
next prev parent reply other threads:[~2022-05-12 22:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 18:11 Apparent regression in blktests since 5.18-rc1+ Bob Pearson
2022-05-07 0:10 ` Bart Van Assche
2022-05-07 0:29 ` Yanjun Zhu
2022-05-07 1:29 ` Jason Gunthorpe
2022-05-07 1:55 ` Yanjun Zhu
2022-05-07 13:43 ` Bob Pearson
2022-05-08 4:13 ` Bart Van Assche
2022-05-10 15:24 ` Pearson, Robert B
2022-05-12 21:57 ` Bob Pearson
2022-05-12 22:25 ` Bart Van Assche [this message]
2022-05-13 0:41 ` Bob Pearson
2022-05-13 3:40 ` Bart Van Assche
2022-05-17 15:21 ` Bob Pearson
2022-05-17 20:44 ` Bart Van Assche
2022-05-17 20:54 ` Bob Pearson
2022-05-17 20:59 ` Bob Pearson
2022-05-08 8:43 ` Yanjun Zhu
2022-05-09 8:01 ` Zhu Yanjun
2022-05-09 11:52 ` Jason Gunthorpe
2022-05-09 12:31 ` Yanjun Zhu
2022-05-09 12:33 ` Jason Gunthorpe
2022-05-09 12:42 ` Yanjun Zhu
2022-05-07 13:40 ` Bob Pearson
2022-05-09 6:56 ` Thorsten Leemhuis
2022-05-10 3:53 ` Bart Van Assche
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=529dbb0a-0b75-9752-62a3-a1235565aa1a@acm.org \
--to=bvanassche@acm.org \
--cc=bmt@zurich.ibm.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox