From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [patch 0/6] init declaration cleanup
Date: Sun, 12 Mar 2006 16:47:06 +0000 [thread overview]
Message-ID: <200603121647.k2CGl4g09972@unix-os.sc.intel.com> (raw)
I started off at mca.c, surfing around the source tree, made
some changes, then made more changes. And I end up with 37
instances with the following diffstat.
arch/ia64/kernel/mca.c | 12 ++++-----
arch/ia64/kernel/patch.c | 8 +++---
arch/ia64/kernel/setup.c | 24 +++++++++----------
arch/ia64/kernel/vmlinux.lds.S | 51 ++++++++++++++++++++---------------------
arch/ia64/mm/contig.c | 8 +++---
arch/ia64/mm/discontig.c | 2 -
arch/ia64/mm/init.c | 16 ++++++------
include/asm-ia64/processor.h | 1
8 files changed, 61 insertions(+), 61 deletions(-)
The end result? Moved 15,176 byte worth of text and data into
init section, which netted a "whooping" one extra free page. Do
I care about that extra page? Probably not. Nevertheless, post
them so that next poor soul won't waste his time trying to
duplicate the effort.
- Ken
reply other threads:[~2006-03-12 16:47 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=200603121647.k2CGl4g09972@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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