From: Bart Van Assche <bvanassche@acm.org>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"nbd@other.debian.org" <nbd@other.debian.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: blktests failures with v6.10-rc1 kernel
Date: Fri, 31 May 2024 13:08:52 -0700 [thread overview]
Message-ID: <0a82785a-a417-4f53-8f3a-2a9ad3ab3bf7@acm.org> (raw)
In-Reply-To: <CAD=hENdBGcBSzcaniH+En6gecpay7S-fm1foEg5vmuXiVYxhpQ@mail.gmail.com>
On 5/31/24 13:06, Zhu Yanjun wrote:
> On Fri, May 31, 2024 at 10:01 PM Bart Van Assche <bvanassche@acm.org> wrote:
>>
>> On 5/31/24 07:35, Zhu Yanjun wrote:
>>> IIRC, the problem with srp/002, 011 also occurs with siw driver, do you make
>>> tests with siw driver to verify whether the problem with srp/002, 011 is also > fixed or not?
>>
>> I have not yet seen any failures of any of the SRP tests when using the siw driver.
>> What am I missing?
>
> (left out a bunch of forwarded emails)
Forwarding emails is not useful, especially if these emails do not answer the question
that I asked.
Thanks,
Bart.
next prev parent reply other threads:[~2024-05-31 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 1:54 blktests failures with v6.10-rc1 kernel Shinichiro Kawasaki
2024-05-31 14:35 ` Zhu Yanjun
2024-05-31 20:01 ` Bart Van Assche
2024-05-31 20:06 ` Zhu Yanjun
2024-05-31 20:08 ` Bart Van Assche [this message]
2024-05-31 20:35 ` Zhu Yanjun
2024-05-31 20:46 ` Bart Van Assche
2024-06-01 1:49 ` Zhu Yanjun
2024-06-04 6:57 ` Shinichiro Kawasaki
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=0a82785a-a417-4f53-8f3a-2a9ad3ab3bf7@acm.org \
--to=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox