From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Travis <travis@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, Len Brown <len.brown@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jack Steiner <steiner@sgi.com>, Robin Holt <holt@sgi.com>,
Lori Gilbertson <loriann@sgi.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/6] printk: Allocate kernel log buffer earlier
Date: Thu, 20 Jan 2011 16:07:16 -0800 [thread overview]
Message-ID: <20110120160716.d65c308b.akpm@linux-foundation.org> (raw)
In-Reply-To: <4D38CB72.2060503@sgi.com>
On Thu, 20 Jan 2011 15:55:30 -0800
Mike Travis <travis@sgi.com> wrote:
> If I have:
>
> void __init setup(void)
> {
> static int data;
> ...
>
> Does data automatically get put into the initdata section? Or does
> it need the __initdata tag as well?
It needs __initdata. gcc doesn't know that __init and __initdata are
related things - as far as the compiler is concerned, they're all just
sections.
next prev parent reply other threads:[~2011-01-21 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 23:01 [PATCH 0/6] init: Shrink early messages to prevent overflowing the kernel log buffer Mike Travis
2011-01-19 23:01 ` [PATCH 1/6] printk: Allocate kernel log buffer earlier Mike Travis
2011-01-20 23:50 ` Andrew Morton
2011-01-20 23:55 ` Mike Travis
2011-01-21 0:07 ` Andrew Morton [this message]
2011-01-19 23:01 ` [PATCH 2/6] ACPI: Minimize X2APIC initial messages Mike Travis
2011-01-19 23:01 ` [PATCH 3/6] x86: Minimize initial Bootmem messages Mike Travis
2011-01-19 23:01 ` [PATCH 4/6] x86: Minimize initial e820 messages Mike Travis
2011-01-19 23:01 ` [PATCH 5/6] x86: Minimize SRAT messages Mike Travis
2011-01-19 23:01 ` [PATCH 6/6] printk: Minimize time zero output Mike Travis
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=20110120160716.d65c308b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=holt@sgi.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loriann@sgi.com \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@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.