All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH v5 2/6] mm: export add_swap_extent()
Date: Fri, 31 Aug 2018 15:36:37 -0700	[thread overview]
Message-ID: <b0001941b7d21c3caec4878d035e95d08bf586b2.1535754957.git.osandov@fb.com> (raw)
In-Reply-To: <cover.1535754957.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

  parent reply	other threads:[~2018-09-01  2:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 22:36 [PATCH v5 0/6] Btrfs: implement swap file support Omar Sandoval
2018-08-31 22:36 ` [PATCH v5 1/6] mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS Omar Sandoval
2018-08-31 22:36 ` Omar Sandoval [this message]
2018-08-31 22:36 ` [PATCH v5 3/6] vfs: update swap_{,de}activate documentation Omar Sandoval
2018-08-31 22:36 ` [PATCH v5 4/6] Btrfs: prevent ioctls from interfering with a swap file Omar Sandoval
2018-08-31 22:36 ` [PATCH v5 5/6] Btrfs: rename get_chunk_map() and make it non-static Omar Sandoval
2018-08-31 22:36 ` [PATCH v5 6/6] Btrfs: support swap files Omar Sandoval
2018-09-06 11:59 ` [PATCH v5 0/6] Btrfs: implement swap file support David Sterba
2018-09-06 18:08   ` 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=b0001941b7d21c3caec4878d035e95d08bf586b2.1535754957.git.osandov@fb.com \
    --to=osandov@osandov.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@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.