From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, dingel@linux.vnet.ibm.com,
mm-commits@vger.kernel.org
Subject: [folded-merged] mm-memoryc-remove-unused-code-from-do_wp_page-fix.patch removed from -mm tree
Date: Wed, 12 Dec 2012 13:41:48 -0800 [thread overview]
Message-ID: <20121212214149.02C3382004A@wpzn4.hot.corp.google.com> (raw)
The patch titled
Subject: mm-memoryc-remove-unused-code-from-do_wp_page-fix
has been removed from the -mm tree. Its filename was
mm-memoryc-remove-unused-code-from-do_wp_page-fix.patch
This patch was dropped because it was folded into mm-memoryc-remove-unused-code-from-do_wp_page.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-memoryc-remove-unused-code-from-do_wp_page-fix
cleanup
Cc: Dominik Dingel <dingel@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff -puN mm/memory.c~mm-memoryc-remove-unused-code-from-do_wp_page-fix mm/memory.c
--- a/mm/memory.c~mm-memoryc-remove-unused-code-from-do_wp_page-fix
+++ a/mm/memory.c
@@ -2780,9 +2780,8 @@ unlock:
oom_free_new:
page_cache_release(new_page);
oom:
- if (old_page) {
+ if (old_page)
page_cache_release(old_page);
- }
return VM_FAULT_OOM;
unwritable_page:
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
origin.patch
thp-implement-splitting-pmd-for-huge-zero-page.patch
mm-add-a-reminder-comment-for-__gfp_bits_shift.patch
numa-add-config_movable_node-for-movable-dedicated-node.patch
mm-introduce-new-field-managed_pages-to-struct-zone.patch
mm-provide-more-accurate-estimation-of-pages-occupied-by-memmap.patch
tmpfs-support-seek_data-and-seek_hole-reprise.patch
hwpoison-hugetlbfs-fix-rss-counter-warning.patch
mm-memoryc-remove-unused-code-from-do_wp_page.patch
reply other threads:[~2012-12-12 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121212214149.02C3382004A@wpzn4.hot.corp.google.com \
--to=akpm@linux-foundation.org \
--cc=dingel@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox