Commit 26d7b99b authored by Uwe Kleine-König's avatar Uwe Kleine-König Committed by Linus Torvalds

lib/test-kstrtox.c: mark const init data with __initconst instead of __initdata

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.
Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
Cc: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 17a801f4
...@@ -11,7 +11,7 @@ struct test_fail { ...@@ -11,7 +11,7 @@ struct test_fail {
}; };
#define DEFINE_TEST_FAIL(test) \ #define DEFINE_TEST_FAIL(test) \
const struct test_fail test[] __initdata const struct test_fail test[] __initconst
#define DECLARE_TEST_OK(type, test_type) \ #define DECLARE_TEST_OK(type, test_type) \
test_type { \ test_type { \
...@@ -21,7 +21,7 @@ struct test_fail { ...@@ -21,7 +21,7 @@ struct test_fail {
} }
#define DEFINE_TEST_OK(type, test) \ #define DEFINE_TEST_OK(type, test) \
const type test[] __initdata const type test[] __initconst
#define TEST_FAIL(fn, type, fmt, test) \ #define TEST_FAIL(fn, type, fmt, test) \
{ \ { \
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment