The patch titled
Subject: scripts/tags.sh: add __ro_after_init
has been added to the -mm tree. Its filename is
scripts-tagssh-add-__ro_after_init.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/scripts-tagssh-add-__ro_after_init.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/scripts-tagssh-add-__ro_after_init.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: Constantine Shulyupin <const@xxxxxxxxxxxxx>
Subject: scripts/tags.sh: add __ro_after_init
Link: http://lkml.kernel.org/r/20180711183646.4022-1-const@xxxxxxxxxxxxx
Signed-off-by: Constantine Shulyupin <const@xxxxxxxxxxxxx>
Cc: Joey Pabalinas <joeypabalinas@xxxxxxxxx>
Cc: Masahiro Yamada <yamada.masahiro@xxxxxxxxxxxxx>
Cc: Matthew Wilcox <willy@xxxxxxxxxxxxx>
Cc: Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
scripts/tags.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN scripts/tags.sh~scripts-tagssh-add-__ro_after_init scripts/tags.sh
--- a/scripts/tags.sh~scripts-tagssh-add-__ro_after_init
+++ a/scripts/tags.sh
@@ -245,7 +245,7 @@ exuberant()
{
setup_regex exuberant asm c
all_target_sources | xargs $1 -a \
- -I __initdata,__exitdata,__initconst, \
+ -I __initdata,__exitdata,__initconst,__ro_after_init \
-I __initdata_memblock \
-I __refdata,__attribute,__maybe_unused,__always_unused \
-I __acquires,__releases,__deprecated \
_
Patches currently in -mm which might be from const@xxxxxxxxxxxxx are
scripts-tagssh-add-__ro_after_init.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
