The patch titled Subject: shmem: fix compilation warnings on unused functions has been removed from the -mm tree. Its filename was shmem-fix-compilation-warnings-on-unused-functions.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx> Subject: shmem: fix compilation warnings on unused functions Compiling shmem.c with CONFIG_SHMEM and CONFIG_TRANSAPRENT_HUGE_PAGECACHE enabled raises warnings on two unused functions when CONFIG_TMPFS and CONFIG_SYSFS are both disabled: mm/shmem.c:390:20: warning: `shmem_format_huge' defined but not used [-Wunused-function] static const char *shmem_format_huge(int huge) ^~~~~~~~~~~~~~~~~ mm/shmem.c:373:12: warning: `shmem_parse_huge' defined but not used [-Wunused-function] static int shmem_parse_huge(const char *str) ^~~~~~~~~~~~~~~~ A conditional compilation on tmpfs or sysfs removes the warnings. Link: http://lkml.kernel.org/r/20161118055749.11313-1-jeremy.lefaure@xxxxxxxxxxxx Signed-off-by: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx> Acked-by: Hugh Dickins <hughd@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/shmem.c | 2 ++ 1 file changed, 2 insertions(+) diff -puN mm/shmem.c~shmem-fix-compilation-warnings-on-unused-functions mm/shmem.c --- a/mm/shmem.c~shmem-fix-compilation-warnings-on-unused-functions +++ a/mm/shmem.c @@ -370,6 +370,7 @@ static bool shmem_confirm_swap(struct ad int shmem_huge __read_mostly; +#if defined(CONFIG_SYSFS) || defined(CONFIG_TMPFS) static int shmem_parse_huge(const char *str) { if (!strcmp(str, "never")) @@ -407,6 +408,7 @@ static const char *shmem_format_huge(int return "bad_val"; } } +#endif static unsigned long shmem_unused_huge_shrink(struct shmem_sb_info *sbinfo, struct shrink_control *sc, unsigned long nr_to_split) _ Patches currently in -mm which might be from jeremy.lefaure@xxxxxxxxxxxx are -- 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