From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, consul.kautuk@gmail.com,
mm-commits@vger.kernel.org
Subject: [folded] mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix.patch removed from -mm tree
Date: Mon, 31 Oct 2011 16:46:17 -0700 [thread overview]
Message-ID: <201110312346.p9VNkIA5020049@wpaz1.hot.corp.google.com> (raw)
The patch titled
Subject: mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix
has been removed from the -mm tree. Its filename was
mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix.patch
This patch was dropped because it was folded into mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks.patch
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix
Cc: Kautuk Consul <consul.kautuk@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mmap.c | 1 -
1 file changed, 1 deletion(-)
diff -puN mm/mmap.c~mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix mm/mmap.c
--- a/mm/mmap.c~mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks-fix
+++ a/mm/mmap.c
@@ -2582,7 +2582,6 @@ int mm_take_all_locks(struct mm_struct *
out_unlock:
mm_drop_all_locks(mm);
-
return -EINTR;
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
origin.patch
dma-mapping-fix-sync_single_range_-dma-debugging.patch
include-linux-dmarh-forward-declare-struct-acpi_dmar_header.patch
proc-self-numa_maps-restore-huge-tag-for-hugetlb-vmas.patch
mm-add-comments-to-explain-mm_struct-fields.patch
mm-avoid-null-pointer-access-in-vm_struct-via-proc-vmallocinfo.patch
thp-mremap-support-and-tlb-optimization.patch
mm-neaten-warn_alloc_failed.patch
debug-pagealloc-add-support-for-highmem-pages.patch
mm-add-comment-explaining-task-state-setting-in-bdi_forker_thread-fix.patch
mm-mmapc-eliminate-the-ret-variable-from-mm_take_all_locks.patch
mm-munlock-use-mapcount-to-avoid-terrible-overhead-fix.patch
kernel-sysctlc-add-cap_last_cap-to-proc-sys-kernel-fix.patch
drivers-leds-leds-lp5521c-check-if-reset-is-successful-fix.patch
lib-bitmapc-quiet-sparse-noise-about-address-space-fix.patch
llist-return-whether-list-is-empty-before-adding-in-llist_add-fix.patch
checkpatch-add-a-strict-check-for-utf-8-in-commit-logs.patch
reply other threads:[~2011-10-31 23:46 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=201110312346.p9VNkIA5020049@wpaz1.hot.corp.google.com \
--to=akpm@linux-foundation.org \
--cc=consul.kautuk@gmail.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 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.