From: syzbot ci <syzbot+cicb7c662f3b6cb6a1@syzkaller.appspotmail.com>
To: syzbot@syzkaller.appspotmail.com, jbingham@gmail.com,
syzbot@lists.linux.dev
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: minix: convert to iomap and add direct I/O
Date: Fri, 26 Jun 2026 14:00:39 -0700 [thread overview]
Message-ID: <6a3ee877.bd346d9a.250aae.000c.GAE@google.com> (raw)
In-Reply-To: <6a3edf5e.80e5668d.5d0ef.000c.GAE@google.com>
syzbot ci has tested the suggested fix patch on top of the following series:
[v1] minix: convert to iomap and add direct I/O
https://lore.kernel.org/all/cover.1782422707.git.jbingham@gmail.com
Patch: https://ci.syzbot.org/jobs/5d331341-e1eb-4c99-9d8a-2b0ec62b64a8/patch
The patch testing request could not be completed:
job has no testing tasks available
Full report is available here:
https://ci.syzbot.org/session/ae259067-e412-4404-a607-9b4bd5725284
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2026-06-26 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260626202118.2464544-1-jbingham@gmail.com>
2026-06-26 20:21 ` Forwarded: [syzbot ci] Re: minix: convert to iomap and add direct I/O syzbot
2026-06-26 20:50 ` syzbot ci
2026-06-26 20:21 ` Forwarded: " syzbot
2026-06-26 20:54 ` syzbot ci
2026-06-26 20:21 ` Forwarded: " syzbot
2026-06-26 21:00 ` syzbot ci [this message]
[not found] <cover.1782619718.git.jbingham@gmail.com>
2026-06-29 5:27 ` syzbot ci
2026-06-30 3:05 ` Jeremy Bingham
2026-06-30 4:05 ` syzbot ci
2026-06-26 19:26 Forwarded: " syzbot
2026-06-26 20:13 ` syzbot ci
-- strict thread matches above, loose matches on Subject: below --
2026-06-26 19:26 Forwarded: " syzbot
2026-06-26 20:18 ` syzbot ci
2026-06-26 19:25 Forwarded: " syzbot
2026-06-26 20:00 ` syzbot ci
[not found] <cover.1782422707.git.jbingham@gmail.com>
2026-06-26 7:07 ` syzbot ci
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=6a3ee877.bd346d9a.250aae.000c.GAE@google.com \
--to=syzbot+cicb7c662f3b6cb6a1@syzkaller.appspotmail.com \
--cc=jbingham@gmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzbot@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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