From: rajman mekaco <rajman.mekaco@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Tejun Heo <tj@kernel.org>, Minchan Kim <minchan.kim@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
rajman mekaco <rajman.mekaco@gmail.com>
Subject: [PATCH 1/1] page_alloc.c: remove argument to pageblock_default_order
Date: Thu, 3 May 2012 22:45:12 +0530 [thread overview]
Message-ID: <1336065312-2891-1-git-send-email-rajman.mekaco@gmail.com> (raw)
When CONFIG_HUGETLB_PAGE_SIZE_VARIABLE is not defined, then
pageblock_default_order has an argument to it.
However, free_area_init_core will call it without any argument
anyway.
Remove the argument to pageblock_default_order when
CONFIG_HUGETLB_PAGE_SIZE_VARIABLE is not defined.
Signed-off-by: rajman mekaco <rajman.mekaco@gmail.com>
---
mm/page_alloc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index a712fb9..4b95412 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -4274,7 +4274,7 @@ static inline void __init set_pageblock_order(unsigned int order)
* at compile-time. See include/linux/pageblock-flags.h for the values of
* pageblock_order based on the kernel config
*/
-static inline int pageblock_default_order(unsigned int order)
+static inline int pageblock_default_order(void)
{
return MAX_ORDER-1;
}
--
1.7.5.4
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-05-03 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:15 rajman mekaco [this message]
2012-05-03 23:37 ` [PATCH 1/1] page_alloc.c: remove argument to pageblock_default_order Andrew Morton
2012-05-10 13:34 ` Mel Gorman
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=1336065312-2891-1-git-send-email-rajman.mekaco@gmail.com \
--to=rajman.mekaco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=minchan.kim@gmail.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).