From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, ak@linux.intel.com,
mm-commits@vger.kernel.org
Subject: [folded] mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes.patch removed from -mm tree
Date: Tue, 22 Mar 2011 16:01:06 -0700 [thread overview]
Message-ID: <201103222301.p2MN16Zd000331@imap1.linux-foundation.org> (raw)
The patch titled
mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes
has been removed from the -mm tree. Its filename was
mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes.patch
This patch was dropped because it was folded into mm-use-__gfp_other_node-for-transparent-huge-pages.patch
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes
From: Andrew Morton <akpm@linux-foundation.org>
ERROR: trailing whitespace
#66: FILE: mm/huge_memory.c:803:
+^I^Ipages[i] = alloc_page_vma_node(GFP_HIGHUSER_MOVABLE | $
total: 1 errors, 0 warnings, 62 lines checked
NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
scripts/cleanfile
./patches/mm-use-__gfp_other_node-for-transparent-huge-pages.patch has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/huge_memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/huge_memory.c~mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes mm/huge_memory.c
--- a/mm/huge_memory.c~mm-use-__gfp_other_node-for-transparent-huge-pages-checkpatch-fixes
+++ a/mm/huge_memory.c
@@ -800,7 +800,7 @@ static int do_huge_pmd_wp_page_fallback(
}
for (i = 0; i < HPAGE_PMD_NR; i++) {
- pages[i] = alloc_page_vma_node(GFP_HIGHUSER_MOVABLE |
+ pages[i] = alloc_page_vma_node(GFP_HIGHUSER_MOVABLE |
__GFP_OTHER_NODE,
vma, address, page_to_nid(page));
if (unlikely(!pages[i] ||
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
origin.patch
include-asm-generic-unistdh-fix-syncfs-syscall-number.patch
leds-convert-bd2802-driver-to-dev_pm_ops.patch
mm-vmap-area-cache.patch
mm-allow-gup-to-fail-instead-of-waiting-on-a-page.patch
mm-batch-free-pcp-list-if-possible.patch
pagewalk-only-split-huge-pages-when-necessary.patch
mm-compaction-minimise-the-time-irqs-are-disabled-while-isolating-pages-for-migration.patch
mm-add-__gfp_other_node-flag.patch
mm-use-__gfp_other_node-for-transparent-huge-pages.patch
drivers-misc-hmc6352c-fix-wrong-return-value-checking-for-i2c_master_recv-fix.patch
kernel-cpuc-fix-many-errors-related-to-style-fix.patch
calibrate-retry-with-wider-bounds-when-converge-seems-to-fail-fix.patch
kernel-watchdogc-allow-hardlockup-to-panic-by-default-fix.patch
epoll-fix-compiler-warning-and-optimize-the-non-blocking-path.patch
fs-coda-fix-compile-warning-when-config_sysctl=n-fix.patch
documentation-vm-page-typesc-auto-debugfs-mount-for-hwpoison-operation-fix.patch
documentation-vm-page-typesc-auto-debugfs-mount-for-hwpoison-operation-fix-fix.patch
reply other threads:[~2011-03-22 23:01 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=201103222301.p2MN16Zd000331@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.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.