From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com, linux-mm@kvack.org
Subject: [PATCH v6 2/6] mm: export add_swap_extent()
Date: Fri, 7 Sep 2018 00:39:16 -0700 [thread overview]
Message-ID: <6846192edded07fb0cccf11ef37aebd4822275a1.1536305017.git.osandov@fb.com> (raw)
In-Reply-To: <cover.1536305017.git.osandov@fb.com>
From: Omar Sandoval <osandov@fb.com>
Btrfs will need this for swap file support.
Signed-off-by: Omar Sandoval <osandov@fb.com>
---
mm/swapfile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/swapfile.c b/mm/swapfile.c
index d3f95833d12e..51cb30de17bc 100644
--- a/mm/swapfile.c
+++ b/mm/swapfile.c
@@ -2365,6 +2365,7 @@ add_swap_extent(struct swap_info_struct *sis, unsigned long start_page,
list_add_tail(&new_se->list, &sis->first_swap_extent.list);
return 1;
}
+EXPORT_SYMBOL_GPL(add_swap_extent);
/*
* A `swap extent' is a simple thing which maps a contiguous range of pages
--
2.18.0
next prev parent reply other threads:[~2018-09-07 7:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 7:39 [PATCH v6 0/6] Btrfs: implement swap file support Omar Sandoval
2018-09-07 7:39 ` [PATCH v6 1/6] mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS Omar Sandoval
2018-09-07 7:39 ` Omar Sandoval [this message]
2018-09-07 7:39 ` [PATCH v6 3/6] vfs: update swap_{,de}activate documentation Omar Sandoval
2018-09-07 7:39 ` [PATCH v6 4/6] Btrfs: prevent ioctls from interfering with a swap file Omar Sandoval
2018-09-07 7:39 ` [PATCH v6 5/6] Btrfs: rename get_chunk_map() and make it non-static Omar Sandoval
2018-09-07 7:54 ` Nikolay Borisov
2018-09-07 10:26 ` David Sterba
2018-09-07 7:39 ` [PATCH v6 6/6] Btrfs: support swap files Omar Sandoval
2018-09-07 8:39 ` Nikolay Borisov
2018-09-07 18:04 ` Omar Sandoval
2018-09-07 18:17 ` Omar Sandoval
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=6846192edded07fb0cccf11ef37aebd4822275a1.1536305017.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox