All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: hch@infradead.org, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 01/11] iomap: start moving code to fs/iomap/
Date: Mon, 01 Jul 2019 10:02:05 -0700	[thread overview]
Message-ID: <156200052577.1790352.9825618388583583693.stgit@magnolia> (raw)
In-Reply-To: <156200051933.1790352.5147420943973755350.stgit@magnolia>

From: Darrick J. Wong <darrick.wong@oracle.com>

Create the build infrastructure we need to start migrating iomap code to
fs/iomap/ from fs/iomap.c.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 MAINTAINERS       |    1 +
 fs/Makefile       |    1 +
 fs/iomap/Makefile |    7 +++++++
 3 files changed, 9 insertions(+)
 create mode 100644 fs/iomap/Makefile


diff --git a/MAINTAINERS b/MAINTAINERS
index 57f496cff999..8ce7d57e4d30 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8222,6 +8222,7 @@ L:	linux-fsdevel@vger.kernel.org
 T:	git git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
 S:	Supported
 F:	fs/iomap.c
+F:	fs/iomap/
 F:	include/linux/iomap.h
 
 IOMMU DRIVERS
diff --git a/fs/Makefile b/fs/Makefile
index c9aea23aba56..8e61bdf9f330 100644
--- a/fs/Makefile
+++ b/fs/Makefile
@@ -53,6 +53,7 @@ obj-$(CONFIG_SYSCTL)		+= drop_caches.o
 
 obj-$(CONFIG_FHANDLE)		+= fhandle.o
 obj-$(CONFIG_FS_IOMAP)		+= iomap.o
+obj-y				+= iomap/
 
 obj-y				+= quota/
 
diff --git a/fs/iomap/Makefile b/fs/iomap/Makefile
new file mode 100644
index 000000000000..b778a05acac3
--- /dev/null
+++ b/fs/iomap/Makefile
@@ -0,0 +1,7 @@
+# SPDX-License-Identifier: GPL-2.0-or-newer
+#
+# Copyright (c) 2019 Oracle.
+# All Rights Reserved.
+#
+
+ccflags-y += -I $(srctree)/$(src)/..


  reply	other threads:[~2019-07-01 17:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 17:01 [PATCH RFC 00/11] iomap: regroup code by functional area Darrick J. Wong
2019-07-01 17:02 ` Darrick J. Wong [this message]
2019-07-01 17:02 ` [PATCH 02/11] iomap: move the swapfile code into a separate file Darrick J. Wong
2019-07-01 17:02 ` [PATCH 03/11] iomap: move the file mapping reporting " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 04/11] iomap: move the SEEK_HOLE " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 05/11] iomap: move the direct IO " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 06/11] iomap: move the buffered write " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 07/11] iomap: move the buffered read " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 08/11] iomap: move the page management " Darrick J. Wong
2019-07-01 17:02 ` [PATCH 09/11] iomap: move the page migration " Darrick J. Wong
2019-07-01 17:03 ` [PATCH 10/11] iomap: move the main iteration " Darrick J. Wong
2019-07-01 17:03 ` [PATCH 11/11] iomap: move internal declarations into fs/iomap/ Darrick J. Wong
2019-07-01 17:41 ` [PATCH RFC 00/11] iomap: regroup code by functional area Theodore Ts'o
2019-07-01 17:59   ` Darrick J. Wong
2019-07-08 18:46 ` Christoph Hellwig
2019-07-09 16:49   ` Darrick J. Wong
2019-07-09 18:12     ` Christoph Hellwig
2019-07-15 16:43       ` Darrick J. Wong
2019-07-15 16:50         ` Christoph Hellwig
2019-07-15 17:49           ` Darrick J. Wong

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=156200052577.1790352.9825618388583583693.stgit@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@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.