The patch titled
Subject: init/main.c: use __initdata instead of __initconst
has been added to the -mm tree. Its filename is
init-fixed-an-error-caused-by-using-__initdata-instead-of-__initconst.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/init-fixed-an-error-caused-by-using-__initdata-instead-of-__initconst.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/init-fixed-an-error-caused-by-using-__initdata-instead-of-__initconst.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Carlos Guerrero Alvarez <carlosteniswarrior@xxxxxxxxx>
Subject: init/main.c: use __initdata instead of __initconst
Link: http://lkml.kernel.org/r/20200106020217.13234-1-carlosteniswarrior@xxxxxxxxx
Signed-off-by: Carlos Guerrero Alvarez <carlosteniswarrior@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
init/main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/init/main.c~init-fixed-an-error-caused-by-using-__initdata-instead-of-__initconst
+++ a/init/main.c
@@ -979,7 +979,7 @@ static initcall_entry_t *initcall_levels
};
/* Keep these in sync with initcalls in include/linux/init.h */
-static const char *initcall_level_names[] __initdata = {
+static const char *initcall_level_names[] __initconst = {
"pure",
"core",
"postcore",
_
Patches currently in -mm which might be from carlosteniswarrior@xxxxxxxxx are
init-fixed-an-error-caused-by-using-__initdata-instead-of-__initconst.patch
