From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Andrew Morton <akpm@linux-foundation.org>, Li Zefan <lizefan@huawei.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH 0/5] mm: Some .text savings
Date: Tue, 3 Feb 2015 00:50:11 +0100 [thread overview]
Message-ID: <1422921016-27618-1-git-send-email-linux@rasmusvillemoes.dk> (raw)
Only compile-tested, but I think these should be ok. Net saving aroung
450 bytes of .text.
Rasmus Villemoes (5):
mm/internal.h: Don't split printk call in two
mm/page_alloc.c: Pull out init code from build_all_zonelists
mm/mm_init.c: Mark mminit_verify_zonelist as __init
mm/mm_init.c: Mark mminit_loglevel __meminitdata
kernel/cpuset.c: Mark cpuset_init_current_mems_allowed as __init
kernel/cpuset.c | 2 +-
mm/internal.h | 6 ++++--
mm/mm_init.c | 4 ++--
mm/page_alloc.c | 17 ++++++++++++++---
4 files changed, 21 insertions(+), 8 deletions(-)
--
2.1.3
--
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:[~2015-02-02 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 23:50 Rasmus Villemoes [this message]
2015-02-02 23:50 ` [PATCH 1/5] mm/internal.h: Don't split printk call in two Rasmus Villemoes
2015-02-02 23:50 ` [PATCH 2/5] mm/page_alloc.c: Pull out init code from build_all_zonelists Rasmus Villemoes
2015-02-03 0:25 ` David Rientjes
2015-02-03 9:57 ` Rasmus Villemoes
2015-02-02 23:50 ` [PATCH 3/5] mm/mm_init.c: Mark mminit_verify_zonelist as __init Rasmus Villemoes
2015-02-02 23:50 ` [PATCH 4/5] mm/mm_init.c: Mark mminit_loglevel __meminitdata Rasmus Villemoes
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=1422921016-27618-1-git-send-email-linux@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
/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).