From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Jan Kara <jack@suse.cz>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCHv2 0/5] get_user_pages() cleanup
Date: Thu, 24 Apr 2014 23:45:13 +0300 [thread overview]
Message-ID: <1398372318-26612-1-git-send-email-kirill.shutemov@linux.intel.com> (raw)
Hi Andrew,
Here's my attempt to cleanup of get_user_pages() code in order to make it
more maintainable.
v2:
- rebased to current Linus' tree (1b17844b29ae);
- add missing includes;
- s/BUILD_BUG/BUG/;
Kirill A. Shutemov (5):
mm: move get_user_pages()-related code to separate file
mm: extract in_gate_area() case from __get_user_pages()
mm: cleanup follow_page_mask()
mm: extract code to fault in a page from __get_user_pages()
mm: cleanup __get_user_pages()
mm/Makefile | 2 +-
mm/gup.c | 666 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
mm/internal.h | 5 +
mm/memory.c | 645 --------------------------------------------------------
4 files changed, 672 insertions(+), 646 deletions(-)
create mode 100644 mm/gup.c
--
1.9.2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-04-24 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 20:45 Kirill A. Shutemov [this message]
2014-04-24 20:45 ` [PATCHv2 1/5] mm: move get_user_pages()-related code to separate file Kirill A. Shutemov
2014-04-24 20:45 ` [PATCHv2 2/5] mm: extract in_gate_area() case from __get_user_pages() Kirill A. Shutemov
2014-04-24 20:45 ` [PATCHv2 3/5] mm: cleanup follow_page_mask() Kirill A. Shutemov
2014-04-24 20:45 ` [PATCHv2 4/5] mm: extract code to fault in a page from __get_user_pages() Kirill A. Shutemov
2014-04-24 20:45 ` [PATCHv2 5/5] mm: cleanup __get_user_pages() Kirill A. Shutemov
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=1398372318-26612-1-git-send-email-kirill.shutemov@linux.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).