From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-api@vger.kernel.org,
linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [RFC PATCH v2 1/7] statx: add I/O alignment information
Date: Thu, 19 May 2022 00:05:24 -0700 [thread overview]
Message-ID: <YoXsNDG/WMbCzz0x@infradead.org> (raw)
In-Reply-To: <20220518235011.153058-2-ebiggers@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-block@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [RFC PATCH v2 1/7] statx: add I/O alignment information
Date: Thu, 19 May 2022 00:05:24 -0700 [thread overview]
Message-ID: <YoXsNDG/WMbCzz0x@infradead.org> (raw)
In-Reply-To: <20220518235011.153058-2-ebiggers@kernel.org>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-05-19 7:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 23:50 [RFC PATCH v2 0/7] make statx() return I/O alignment information Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 1/7] statx: add " Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-19 7:05 ` Christoph Hellwig [this message]
2022-05-19 7:05 ` Christoph Hellwig
2022-05-19 23:06 ` Darrick J. Wong
2022-05-19 23:06 ` [f2fs-dev] " Darrick J. Wong
2022-05-20 3:27 ` Dave Chinner
2022-05-20 3:27 ` [f2fs-dev] " Dave Chinner
2022-06-14 5:25 ` Eric Biggers
2022-06-14 5:25 ` [f2fs-dev] " Eric Biggers
2022-06-15 13:12 ` Christoph Hellwig
2022-06-15 13:12 ` [f2fs-dev] " Christoph Hellwig
2022-06-16 0:04 ` Eric Biggers
2022-06-16 0:04 ` [f2fs-dev] " Eric Biggers
2022-06-16 6:07 ` Christoph Hellwig
2022-06-16 6:07 ` [f2fs-dev] " Christoph Hellwig
2022-06-16 6:19 ` Eric Biggers
2022-06-16 6:19 ` [f2fs-dev] " Eric Biggers
2022-06-16 6:29 ` Christoph Hellwig
2022-06-16 6:29 ` [f2fs-dev] " Christoph Hellwig
2022-05-20 6:30 ` Eric Biggers
2022-05-20 6:30 ` [f2fs-dev] " Eric Biggers
2022-05-20 11:52 ` Christian Brauner
2022-05-20 11:52 ` [f2fs-dev] " Christian Brauner
2022-05-27 9:02 ` Florian Weimer
2022-05-27 9:02 ` [f2fs-dev] " Florian Weimer
2022-05-27 16:22 ` Darrick J. Wong
2022-05-27 16:22 ` [f2fs-dev] " Darrick J. Wong
2022-05-18 23:50 ` [RFC PATCH v2 2/7] fscrypt: change fscrypt_dio_supported() to prepare for STATX_IOALIGN Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 3/7] ext4: support STATX_IOALIGN Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 4/7] f2fs: move f2fs_force_buffered_io() into file.c Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 5/7] f2fs: don't allow DIO reads but not DIO writes Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 6/7] f2fs: simplify f2fs_force_buffered_io() Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
2022-05-18 23:50 ` [RFC PATCH v2 7/7] f2fs: support STATX_IOALIGN Eric Biggers
2022-05-18 23:50 ` [f2fs-dev] " Eric Biggers
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=YoXsNDG/WMbCzz0x@infradead.org \
--to=hch@infradead.org \
--cc=ebiggers@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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.