From: David Howells <dhowells@redhat.com>
To: Tim Abbott <tabbott@MIT.EDU>
Cc: dhowells@redhat.com, Sam Ravnborg <sam@ravnborg.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Anders Kaseorg <andersk@MIT.EDU>, Waseem Daher <wdaher@MIT.EDU>,
Denys Vlasenko <vda.linux@googlemail.com>,
Jeff Arnold <jbarnold@MIT.EDU>
Subject: Re: [PATCH 5/6] mn10300: use new macros for .data.init_task.
Date: Fri, 01 May 2009 15:46:19 +0100 [thread overview]
Message-ID: <11779.1241189179@redhat.com> (raw)
In-Reply-To: <1241135661-9147-6-git-send-email-tabbott@mit.edu>
Tim Abbott <tabbott@MIT.EDU> wrote:
> .data.init_task should not need a separate output section; this change
> moves it into the .data section.
Hmmm... This causes the kernel I'm building to make an extra page of RAM into
dead space.
David
next prev parent reply other threads:[~2009-05-01 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 23:54 [PATCH 0/6] section name cleanup for mn10300 Tim Abbott
2009-04-30 23:54 ` [PATCH 1/6] mn10300: Use macros for .bss.page_aligned section Tim Abbott
2009-04-30 23:54 ` [PATCH 2/6] mn10300: Drop unused .data.idt section Tim Abbott
2009-04-30 23:54 ` [PATCH 3/6] mn10300: use NOSAVE_DATA macro for .data.nosave section Tim Abbott
2009-04-30 23:54 ` [PATCH 4/6] mn10300: use new macro for .data.cacheline_aligned section Tim Abbott
2009-04-30 23:54 ` [PATCH 5/6] mn10300: use new macros for .data.init_task Tim Abbott
2009-04-30 23:54 ` [PATCH 6/6] mn10300: use new macro for .data.read_mostly section Tim Abbott
2009-05-01 14:46 ` David Howells [this message]
2009-05-01 15:00 ` [PATCH 5/6] mn10300: use new macros for .data.init_task Tim Abbott
2009-05-01 15:11 ` Sam Ravnborg
2009-05-01 14:35 ` [PATCH 0/6] section name cleanup for mn10300 David Howells
2009-05-01 14:48 ` Sam Ravnborg
2009-05-01 15:03 ` David Howells
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=11779.1241189179@redhat.com \
--to=dhowells@redhat.com \
--cc=andersk@MIT.EDU \
--cc=jbarnold@MIT.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tabbott@MIT.EDU \
--cc=vda.linux@googlemail.com \
--cc=wdaher@MIT.EDU \
/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