From: Christoph Hellwig <hch@lst.de>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Yangtao Li <frank.li@vivo.com>, Dave Kleikamp <shaggy@kernel.org>,
Jan Kara <jack@suse.com>, Mark Fasheh <mark@fasheh.com>,
Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, ocfs2-devel@lists.linux.dev
Subject: Re: removing the remaining blockdev_direct_IO users
Date: Thu, 16 Jul 2026 10:18:04 +0200 [thread overview]
Message-ID: <20260716081804.GB12330@lst.de> (raw)
In-Reply-To: <1421ca7e131663e594806f43cdad34f3282bd915.camel@dubeyko.com>
On Wed, Jul 15, 2026 at 05:08:49PM -0700, Viacheslav Dubeyko wrote:
> I have a very initial state of patchset for HFS+ file system. I am
> testing it by xfstests now. As far as I can see, currently, this
> patchset introduced multiple xfstests failures. If you like I can share
> this patchset for discussion and review. Otherwise, let me fix the
> found xfstests failures at first and, then, I'll share the patchset for
> the review.
The unfinished one isn't too interesting to review. But if you're
stuck on failures you need help with, feel free to send it along
with the question.
prev parent reply other threads:[~2026-07-16 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:07 removing the remaining blockdev_direct_IO users Christoph Hellwig
2026-07-10 16:51 ` Viacheslav Dubeyko
2026-07-13 9:58 ` Christoph Hellwig
2026-07-13 22:33 ` Viacheslav Dubeyko
2026-07-16 0:08 ` Viacheslav Dubeyko
2026-07-16 8:18 ` Christoph Hellwig [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=20260716081804.GB12330@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=shaggy@kernel.org \
--cc=slava@dubeyko.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.