[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdbVWnZHzgDuqMdvELjjwte1aJXnghpd_qtqcz3cf6fuXQ@mail.gmail.com>
Date: Tue, 3 Apr 2012 22:28:52 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
kernel@...gutronix.de, Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH 02/17] pinctrl: mark const init data with __initconst
instead of __initdata
2012/3/29 Uwe Kleine-König <u.kleine-koenig@...gutronix.de>:
> 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.
Thanks. applied, U300 compiles fine so I trust you on this
advice!
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists