From: Tony Lindgren <tony@atomide.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
kernel@pengutronix.de, Andrew Victor <linux@maxim.org.za>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Russell King <linux@arm.linux.org.uk>,
Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@ti.com>,
Kukjin Kim <kgene.kim@samsung.com>,
Shawn Guo <shawn.guo@linaro.org>,
Lennert Buytenhek <kernel@wantstofly.org>,
Nicolas Pitre <nico@fluxnic.net>,
Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
David Brown <davidb@codeaurora.org>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Barry Song <baohua.song@csr.com>, Andrew Lunn <andrew@lunn.ch>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-arm-kernel@lists.infradead.org,
davinci-linux-open-source@linux.davincidsp.com, linux-sa
Subject: Re: [PATCH 03/17] ARM: mark const init data with __initconst instead of __initdata
Date: Fri, 30 Mar 2012 09:11:31 -0700 [thread overview]
Message-ID: <20120330161130.GA8240@atomide.com> (raw)
In-Reply-To: <1333055554-31300-3-git-send-email-u.kleine-koenig@pengutronix.de>
* Uwe Kleine-König <u.kleine-koenig@pengutronix.de> [120329 14:16]:
> As long as there is no other non-const variable marked __initdata in the
> same compilation unit it doesn't hurt. If there were one however
> compilation would fail with
>
> error: $variablename causes a section type conflict
>
> because a section containing const variables is marked read only and so
> cannot contain non-const variables.
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2012-03-30 16:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 21:11 [PATCH 00/17] mark const init data with __initconst instead of __initdata Uwe Kleine-König
2012-03-29 21:12 ` [PATCH 03/17] ARM: " Uwe Kleine-König
2012-03-29 22:31 ` David Brown
2012-03-30 4:34 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-30 6:11 ` Shawn Guo
2012-03-30 9:50 ` Uwe Kleine-König
2012-03-30 11:25 ` Shawn Guo
2012-03-30 16:11 ` Tony Lindgren [this message]
2012-03-30 9:59 ` [PATCH 00/17] " Uwe Kleine-König
2012-03-30 20:03 ` [PATCH v2 00/15] " Uwe Kleine-König
2012-03-30 20:04 ` [PATCH v2 02/15] ARM: " Uwe Kleine-König
2012-04-11 11:34 ` Sekhar Nori
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=20120330161130.GA8240@atomide.com \
--to=tony@atomide.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=baohua.song@csr.com \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwalker@fifo99.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@wantstofly.org \
--cc=kgene.kim@samsung.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
--cc=lucas.demarchi@profusion.mobi \
--cc=nico@fluxnic.net \
--cc=nicolas.ferre@atmel.com \
--cc=nsekhar@ti.com \
--cc=plagnioj@jcrosoft.com \
--cc=shawn.guo@linaro.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).