From: Jens Axboe <axboe@kernel.dk>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: build direct-io.c conditionally
Date: Thu, 26 Jan 2023 10:31:25 -0700 [thread overview]
Message-ID: <167475428508.707060.7530877439951509379.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230125065839.191256-1-hch@lst.de>
On Wed, 25 Jan 2023 07:58:37 +0100, Christoph Hellwig wrote:
> this series makes the build of direct-io.c conditional as only
> about a dozen file systems actually use it.
>
> Diffstat:
> Kconfig | 4 ++++
> Makefile | 3 ++-
> affs/Kconfig | 1 +
> direct-io.c | 24 ------------------------
> exfat/Kconfig | 1 +
> ext2/Kconfig | 1 +
> fat/Kconfig | 1 +
> hfs/Kconfig | 1 +
> hfsplus/Kconfig | 1 +
> internal.h | 4 +---
> jfs/Kconfig | 1 +
> nilfs2/Kconfig | 1 +
> ntfs3/Kconfig | 1 +
> ocfs2/Kconfig | 1 +
> reiserfs/Kconfig | 1 +
> super.c | 24 ++++++++++++++++++++++++
> udf/Kconfig | 1 +
> 17 files changed, 43 insertions(+), 28 deletions(-)
>
> [...]
Applied, thanks!
[1/2] fs: move sb_init_dio_done_wq out of direct-io.c
commit: 439bc39b3cf0014b1b75075812f7ef0f8baa9674
[2/2] fs: build the legacy direct I/O code conditionally
commit: 9636e650e16f6b01f0044f7662074958c23e4707
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-01-26 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 6:58 Christoph Hellwig
2023-01-25 6:58 ` [PATCH 1/2] fs: move sb_init_dio_done_wq out of direct-io.c Christoph Hellwig
2023-01-25 9:10 ` Jan Kara
2023-01-25 18:17 ` Eric Biggers
2023-01-25 6:58 ` [PATCH 2/2] fs: build the legacy direct I/O code conditionally Christoph Hellwig
2023-01-25 9:13 ` Jan Kara
2023-01-25 18:18 ` Eric Biggers
2023-01-26 21:20 ` Al Viro
2023-01-27 6:30 ` Christoph Hellwig
2023-01-26 17:31 ` Jens Axboe [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=167475428508.707060.7530877439951509379.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®