linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, yesterday's linux-next build (htmldocs) produced this warning: mm/vmalloc.c:425: warning: expecting prototype for vunmap_range_noflush(). Prototype was for vunmap_range() instead Introduced by commit cde193f42509 ("mm/vmalloc: remove

Re: linux-next: build warning after merge of the akpm-current tree

Em Tue, 16 Mar 2021 17:09:20 -0600 Jonathan Corbet escreveu: > Stephen Rothwell writes: > > [Adding Mauro] > > > On Tue, 16 Mar 2021 11:18:11 -0700 Minchan Kim wrote: > >> > >> On Mon, Mar 15, 2021 at 04:35:22PM +1100, Stephen Rothwell wrote: > >> > Hi all, > >> > > >> > After merging the

Re: linux-next: build warning after merge of the akpm-current tree

Stephen Rothwell writes: [Adding Mauro] > On Tue, 16 Mar 2021 11:18:11 -0700 Minchan Kim wrote: >> >> On Mon, Mar 15, 2021 at 04:35:22PM +1100, Stephen Rothwell wrote: >> > Hi all, >> > >> > After merging the akpm-current tree, today's linux-next build (htmldocs) >> > produced this warning:

Re: linux-next: build warning after merge of the akpm-current tree

Hi Minchan, On Tue, 16 Mar 2021 11:18:11 -0700 Minchan Kim wrote: > > On Mon, Mar 15, 2021 at 04:35:22PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the akpm-current tree, today's linux-next build (htmldocs) > > produced this warning: > > > >

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, Mar 15, 2021 at 04:35:22PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (htmldocs) > produced this warning: > > Documentation/ABI/testing/sysfs-kernel-mm-cma:2: WARNING: Inline interpreted > text or phrase reference

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (htmldocs) produced this warning: Documentation/ABI/testing/sysfs-kernel-mm-cma:2: WARNING: Inline interpreted text or phrase reference start-string without end-string. Introduced by commit 439d477342a3 ("mm: cma: support

Re: linux-next: build warning after merge of the akpm-current tree

Thanks for the report Stephen! Andrew, I have sent you an updated patch. Please let me know if you prefer a follow-up fix instead. BR, Georgi On 12/10/20 11:38, Stephen Rothwell wrote: Hi all, After merging the akpm-current tree, today's linux-next build (htmldocs) produced this warning:

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (htmldocs) produced this warning: Documentation/vm/page_owner.rst:44: WARNING: Literal block ends without a blank line; unexpected unindent. Documentation/vm/page_owner.rst:49: WARNING: Literal block ends without a blank

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, Nov 13, 2020 at 05:01:01PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > WARNING: modpost: missing MODULE_LICENSE() in lib/cmdline_kunit.o > > Introduced by commit > >

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: missing MODULE_LICENSE() in lib/cmdline_kunit.o Introduced by commit f1a15df76475 ("lib/cmdline_kunit: add a new test suite for cmdline API") -- Cheers,

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (htmldocs) produced this warning: include/linux/kfence.h:138: warning: Function parameter or member 'addr' not described in 'kfence_object_start' Introduced by patch mm: add Kernel Electric-Fence infrastructure --

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, Nov 05, 2020 at 06:45:04PM +1100, Anand K. Mistry wrote: > SNIPPED > > > > > > > Looks like left column became too wide, so rather than shift the right > > > column to the right, I'd suggest to drop underscores in Speculation*. > > > > Hm. That makes it inconsistent with

Re: linux-next: build warning after merge of the akpm-current tree

Hi Anand, On Thu, 5 Nov 2020 19:00:11 +1100 Stephen Rothwell wrote: > > On Thu, 5 Nov 2020 18:42:23 +1100 "Anand K. Mistry" > wrote: > > > > How would I go about fixing this? Send a new (v2), fixed patch to the > > mailing list? I'm not that familiar with how patches get merged > > through

Re: linux-next: build warning after merge of the akpm-current tree

Hi Anand, On Thu, 5 Nov 2020 18:42:23 +1100 "Anand K. Mistry" wrote: > > How would I go about fixing this? Send a new (v2), fixed patch to the > mailing list? I'm not that familiar with how patches get merged > through the branches. Since this is in Andrew's quilt series, either a v2, or an

Re: linux-next: build warning after merge of the akpm-current tree

SNIPPED > > > > Looks like left column became too wide, so rather than shift the right > > column to the right, I'd suggest to drop underscores in Speculation*. > > Hm. That makes it inconsistent with Speculation_Store_Bypass. I guess > it's the lesser of two evils. Oh, do you mean renaming the

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, 5 Nov 2020 at 18:03, Mike Rapoport wrote: > > On Thu, Nov 05, 2020 at 05:45:49PM +1100, Stephen Rothwell wrote: > > Hi all, > > > > After merging the akpm-current tree, today's linux-next build (htmldocs) > > produced this warning: > > > > Documentation/filesystems/proc.rst:296: WARNING:

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, Nov 05, 2020 at 05:45:49PM +1100, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (htmldocs) > produced this warning: > > Documentation/filesystems/proc.rst:296: WARNING: Malformed table. > Text in column margin in table line 61. > >

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (htmldocs) produced this warning: Documentation/filesystems/proc.rst:296: WARNING: Malformed table. Text in column margin in table line 61. == === Field

Re: linux-next: build warning after merge of the akpm-current tree

On Tue, 15 Sep 2020 at 06:03, 'David Gow' via kasan-dev wrote: > > [+kasan-dev, +kunit-dev] > > On Mon, Sep 14, 2020 at 3:01 PM Stephen Rothwell > wrote: > > > > Hi all, > > > > After merging the akpm-current tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > >

Re: linux-next: build warning after merge of the akpm-current tree

Hi David, On Tue, 15 Sep 2020 12:03:08 +0800 David Gow wrote: > > > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c: In function > > 'common_nfc_set_geometry': > > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c:514:3: warning: initialization > > discards 'const' qualifier from pointer target type

Re: linux-next: build warning after merge of the akpm-current tree

[+kasan-dev, +kunit-dev] On Mon, Sep 14, 2020 at 3:01 PM Stephen Rothwell wrote: > > Hi all, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > In file included from lib/test_kasan_module.c:16: > lib/../mm/kasan/kasan.h:232:6:

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from lib/test_kasan_module.c:16: lib/../mm/kasan/kasan.h:232:6: warning: conflicting types for built-in function '__asan_register_globals'; expected 'void(void *,

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/madvise.c: In function 'madvise_inject_error': mm/madvise.c:875:15: warning: unused variable 'zone' [-Wunused-variable] 875 | struct zone *zone; | ^~~~

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, Jul 17, 2020 at 08:31:27PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/vmstat.c:614: warning: "MAX_THRESHOLD" redefined > 614 | #define MAX_THRESHOLD 0 > | >

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: mm/vmstat.c:614: warning: "MAX_THRESHOLD" redefined 614 | #define MAX_THRESHOLD 0 | mm/vmstat.c:172: note: this is the location of the previous definition 172 |

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (i386 defconfig) produced this warning: mm/hugetlb.c:49:20: warning: 'hugetlb_cma' defined but not used [-Wunused-variable] 49 | static struct cma *hugetlb_cma[MAX_NUMNODES]; |^~~ Maybe

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: modpost: missing MODULE_LICENSE() in lib/test_bits.o Introduced by commit 37f7d07028d1 ("lib/test_bits.c: add tests of GENMASK") -- Cheers, Stephen Rothwell

Re: linux-next: build warning after merge of the akpm-current tree

Hi Rikard, On Wed, 7 Aug 2019 13:29:17 +0200 Rikard Falkeborn wrote: > > Hi Stephen, Andrew > > On Wed, Aug 07, 2019 at 06:00:41PM +1000, Stephen Rothwell wrote: > > Hi all, > > > > After merging the akpm-current tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > >

Re: linux-next: build warning after merge of the akpm-current tree

Hi Stephen, Andrew On Wed, Aug 07, 2019 at 06:00:41PM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/bits.h:22, > from

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bits.h:22, from arch/x86/include/asm/msr-index.h:5, from arch/x86/boot/cpucheck.c:28: include/linux/build_bug.h:49:

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, 2019-08-01 at 16:39 +1000, Stephen Rothwell wrote: > Hi Miles, > > On Thu, 1 Aug 2019 14:30:03 +0800 Miles Chen wrote: > > > > It's the first time that I receive a build warning after the patch has > > been merged to -mm tree. The build warning had been fixed by Qian, > > should I send

Re: linux-next: build warning after merge of the akpm-current tree

Hi Miles, On Thu, 1 Aug 2019 14:30:03 +0800 Miles Chen wrote: > > It's the first time that I receive a build warning after the patch has > been merged to -mm tree. The build warning had been fixed by Qian, > should I send another change for this? No, that will do. -- Cheers, Stephen Rothwell

Re: linux-next: build warning after merge of the akpm-current tree

On Thu 01-08-19 14:30:03, Miles Chen wrote: [...] > It's the first time that I receive a build warning after the patch has > been merged to -mm tree. The build warning had been fixed by Qian, > should I send another change for this? No need. Andrew has already picked up the fix for mmotm tree

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, 2019-08-01 at 08:15 +0200, Michal Hocko wrote: > On Thu 01-08-19 15:51:30, Stephen Rothwell wrote: > > Hi Miles, > > > > On Wed, 31 Jul 2019 14:28:04 +0800 Miles Chen > > wrote: > > > > > > On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote: > > > > > > > > After merging the

Re: linux-next: build warning after merge of the akpm-current tree

On Thu 01-08-19 15:51:30, Stephen Rothwell wrote: > Hi Miles, > > On Wed, 31 Jul 2019 14:28:04 +0800 Miles Chen wrote: > > > > On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote: > > > > > > After merging the akpm-current tree, today's linux-next build (powerpc > > > ppc64_defconfig)

Re: linux-next: build warning after merge of the akpm-current tree

Hi Miles, On Wed, 31 Jul 2019 14:28:04 +0800 Miles Chen wrote: > > On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote: > > > > After merging the akpm-current tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > mm/memcontrol.c: In function

Re: linux-next: build warning after merge of the akpm-current tree

On 2019/7/31 14:16, Stephen Rothwell wrote: Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/ocfs2/xattr.c:1493:13: warning: 'ocfs2_xa_add_entry' defined but not used [-Wunused-function] static void

Re: linux-next: build warning after merge of the akpm-current tree

On Wed, 2019-07-31 at 16:11 +1000, Stephen Rothwell wrote: > Hi all, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/memcontrol.c: In function 'invalidate_reclaim_iterators': > mm/memcontrol.c:1160:11: warning: suggest

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/ocfs2/xattr.c:1493:13: warning: 'ocfs2_xa_add_entry' defined but not used [-Wunused-function] static void ocfs2_xa_add_entry(struct ocfs2_xa_loc *loc, u32 name_hash)

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: mm/memcontrol.c: In function 'invalidate_reclaim_iterators': mm/memcontrol.c:1160:11: warning: suggest parentheses around assignment used as truth value [-Wparentheses] }

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/infiniband/sw/siw/siw_mem.c: In function 'siw_free_plist': drivers/infiniband/sw/siw/siw_mem.c:66:16: warning: unused variable 'p' [-Wunused-variable] struct page **p =

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: lib/rbtree_test.c: In function 'check_augmented': lib/rbtree_test.c:220:18: warning: unused variable 'rb' [-Wunused-variable] struct rb_node *rb; ^~ Introduced

Re: linux-next: build warning after merge of the akpm-current tree

On Thu, May 30, 2019 at 6:55 AM Stephen Rothwell wrote: > > Hi all, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > net/tipc/sysctl.c:42:12: warning: 'one' defined but not used > [-Wunused-variable] > static int one = 1; >

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: net/tipc/sysctl.c:42:12: warning: 'one' defined but not used [-Wunused-variable] static int one = 1; ^~~ net/tipc/sysctl.c:41:12: warning: 'zero' defined but not used

Re: linux-next: build warning after merge of the akpm-current tree

On Tue, 16 Apr 2019 16:52:56 +1000 Stephen Rothwell wrote: > Hi all, > > On Fri, 29 Mar 2019 13:39:14 +1100 Stephen Rothwell > wrote: > > > > After merging the akpm-current tree, today's linux-next build (arm > > multi_v7_defconfig) produced this warning: > > > > lib/list_sort.c:17:36:

Re: linux-next: build warning after merge of the akpm-current tree

Hi all, On Fri, 29 Mar 2019 13:39:14 +1100 Stephen Rothwell wrote: > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/list_sort.c:17:36: warning: 'pure' attribute ignored [-Wattributes] >struct list_head const *,

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/list_sort.c:17:36: warning: 'pure' attribute ignored [-Wattributes] struct list_head const *, struct list_head const *); ^

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from arch/x86/include/asm/percpu.h:45, from arch/x86/include/asm/current.h:6, from include/linux/sched.h:12, from

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from fs/fat/inode.c:24:0: fs/fat/inode.c: In function '__fat_get_block': fs/fat/inode.c:163:9: warning: format '%ld' expects argument of type 'long int', but

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from fs/fat/inode.c:24:0: fs/fat/inode.c: In function '__fat_get_block': fs/fat/inode.c:163:9: warning: format '%ld' expects argument of type 'long int', but

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, May 07, 2018 at 09:47:54AM -0700, Randy Dunlap wrote: > On 05/07/2018 07:10 AM, Minchan Kim wrote: > > On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: > >> On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > >>> Hi Andrew, > >>> > >>> After merging the akpm-current tree,

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, May 07, 2018 at 09:47:54AM -0700, Randy Dunlap wrote: > On 05/07/2018 07:10 AM, Minchan Kim wrote: > > On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: > >> On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > >>> Hi Andrew, > >>> > >>> After merging the akpm-current tree,

linux-next: build warning after merge of the akpm-current tree

On 05/07/2018 07:10 AM, Minchan Kim wrote: > On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: >> On 05/03/2018 09:17 PM, Stephen Rothwell wrote: >>> Hi Andrew, >>> >>> After merging the akpm-current tree, today's linux-next build >>> (x86_64_allmodconfig) produced this warning: >>>

linux-next: build warning after merge of the akpm-current tree

On 05/07/2018 07:10 AM, Minchan Kim wrote: > On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: >> On 05/03/2018 09:17 PM, Stephen Rothwell wrote: >>> Hi Andrew, >>> >>> After merging the akpm-current tree, today's linux-next build >>> (x86_64_allmodconfig) produced this warning: >>>

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: > On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build > > (x86_64_allmodconfig) produced this warning: > > > > drivers/block/zram/zram_drv.c: In function

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, May 04, 2018 at 08:39:43AM -0700, Randy Dunlap wrote: > On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build > > (x86_64_allmodconfig) produced this warning: > > > > drivers/block/zram/zram_drv.c: In function

Re: linux-next: build warning after merge of the akpm-current tree

On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build > (x86_64_allmodconfig) produced this warning: > > drivers/block/zram/zram_drv.c: In function 'read_block_state': > drivers/block/zram/zram_drv.c:674:16: warning: format

Re: linux-next: build warning after merge of the akpm-current tree

On 05/03/2018 09:17 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build > (x86_64_allmodconfig) produced this warning: > > drivers/block/zram/zram_drv.c: In function 'read_block_state': > drivers/block/zram/zram_drv.c:674:16: warning: format

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64_allmodconfig) produced this warning: drivers/block/zram/zram_drv.c: In function 'read_block_state': drivers/block/zram/zram_drv.c:674:16: warning: format '%llu' expects argument of type 'long long unsigned int',

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64_allmodconfig) produced this warning: drivers/block/zram/zram_drv.c: In function 'read_block_state': drivers/block/zram/zram_drv.c:674:16: warning: format '%llu' expects argument of type 'long long unsigned int',

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memcontrol.c: In function 'memory_events_show': mm/memcontrol.c:5453:23: warning: array subscript is above array bounds [-Warray-bounds]

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memcontrol.c: In function 'memory_events_show': mm/memcontrol.c:5453:23: warning: array subscript is above array bounds [-Warray-bounds]

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux Introduced by commit

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux WARNING: vmlinux: 'abort' exported twice. Previous export was in vmlinux Introduced by commit

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: mm/khugepaged.c: In function 'khugepaged': mm/khugepaged.c:1757:31: warning: 'vma' may be used uninitialized in this function [-Wmaybe-uninitialized] if

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: mm/khugepaged.c: In function 'khugepaged': mm/khugepaged.c:1757:31: warning: 'vma' may be used uninitialized in this function [-Wmaybe-uninitialized] if

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/super.c: In function 'sget_userns': fs/super.c:521:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/super.c: In function 'sget_userns': fs/super.c:521:2: warning: ignoring return value of 'register_shrinker', declared with attribute warn_unused_result [-Wunused-result]

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, Nov 17, 2017 at 4:53 AM, Stephen Rothwell wrote: > Hi all, > > On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell > wrote: >> >> On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: >> > >> > On Mon, Nov 13, 2017 at 9:09

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, Nov 17, 2017 at 4:53 AM, Stephen Rothwell wrote: > Hi all, > > On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell > wrote: >> >> On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: >> > >> > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: >> > > On Mon 13-11-17 16:42:06,

Re: linux-next: build warning after merge of the akpm-current tree

Hi, On 2017/11/17 11:53, Stephen Rothwell wrote: > Hi all, > > On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell > wrote: >> >> On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: >>> >>> On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko

Re: linux-next: build warning after merge of the akpm-current tree

Hi, On 2017/11/17 11:53, Stephen Rothwell wrote: > Hi all, > > On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell > wrote: >> >> On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: >>> >>> On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: On Mon 13-11-17 16:42:06, Stephen

Re: linux-next: build warning after merge of the akpm-current tree

Hi all, On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell wrote: > > On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: > > > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > > On Mon 13-11-17 16:42:06, Stephen

Re: linux-next: build warning after merge of the akpm-current tree

Hi all, On Fri, 17 Nov 2017 09:44:39 +1100 Stephen Rothwell wrote: > > On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: > > > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > > >> > > >> After merging the

Re: linux-next: build warning after merge of the akpm-current tree

Hi all, On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > >> > >> After merging the akpm-current tree, today's linux-next build (powerpc >

Re: linux-next: build warning after merge of the akpm-current tree

Hi all, On Mon, 13 Nov 2017 12:43:08 +0100 Arnd Bergmann wrote: > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > >> > >> After merging the akpm-current tree, today's linux-next build (powerpc > >> ppc64_defconfig) produced this

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 12:54:30, Michal Hocko wrote: > On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > > >> Hi Andrew, > > >> > > >> After merging the akpm-current tree,

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 12:54:30, Michal Hocko wrote: > On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: > > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > > >> Hi Andrew, > > >> > > >> After merging the akpm-current tree, today's linux-next

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, Nov 13, 2017 at 12:54 PM, Michal Hocko wrote: > On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: >> On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: >> > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: >> >> Hi Andrew, >> >> >> >> After merging

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, Nov 13, 2017 at 12:54 PM, Michal Hocko wrote: > On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: >> On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: >> > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: >> >> Hi Andrew, >> >> >> >> After merging the akpm-current tree, today's

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > >> Hi Andrew, > >> > >> After merging the akpm-current tree, today's linux-next build (powerpc > >> ppc64_defconfig)

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 12:43:08, Arnd Bergmann wrote: > On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > >> Hi Andrew, > >> > >> After merging the akpm-current tree, today's linux-next build (powerpc > >> ppc64_defconfig) produced this warning:

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> In file included from

Re: linux-next: build warning after merge of the akpm-current tree

On Mon, Nov 13, 2017 at 9:09 AM, Michal Hocko wrote: > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> In file included from include/linux/mmzone.h:17:0,

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 09:09:55, Michal Hocko wrote: > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > In file included from include/linux/mmzone.h:17:0, >

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 09:09:55, Michal Hocko wrote: > On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (powerpc > > ppc64_defconfig) produced this warning: > > > > In file included from include/linux/mmzone.h:17:0, >

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > In file included from include/linux/mmzone.h:17:0, > from include/linux/mempolicy.h:10, >

Re: linux-next: build warning after merge of the akpm-current tree

On Mon 13-11-17 16:42:06, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > In file included from include/linux/mmzone.h:17:0, > from include/linux/mempolicy.h:10, >

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/printk.h:7:0, from include/linux/kernel.h:14, from lib/test_find_bit.c:28: lib/test_find_bit.c: In function

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/printk.h:7:0, from include/linux/kernel.h:14, from lib/test_find_bit.c:28: lib/test_find_bit.c: In function

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: In file included from include/linux/mmzone.h:17:0, from include/linux/mempolicy.h:10, from mm/mempolicy.c:70: mm/mempolicy.c: In function

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: In file included from include/linux/mmzone.h:17:0, from include/linux/mempolicy.h:10, from mm/mempolicy.c:70: mm/mempolicy.c: In function

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/proc/task_mmu.c: In function 'show_map_vma': fs/proc/task_mmu.c:285:28: warning: unused variable 'priv' [-Wunused-variable] struct proc_maps_private *priv = m->private;

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: fs/proc/task_mmu.c: In function 'show_map_vma': fs/proc/task_mmu.c:285:28: warning: unused variable 'priv' [-Wunused-variable] struct proc_maps_private *priv = m->private;

Re: linux-next: build warning after merge of the akpm-current tree

On 05/26/2017 05:16 AM, Jeff Layton wrote: > On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> fs/jfs/jfs_metapage.c: In function 'force_metapage':

Re: linux-next: build warning after merge of the akpm-current tree

On 05/26/2017 05:16 AM, Jeff Layton wrote: > On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> fs/jfs/jfs_metapage.c: In function 'force_metapage':

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/jfs/jfs_metapage.c: In function 'force_metapage': > fs/jfs/jfs_metapage.c:714:2: warning: ignoring

Re: linux-next: build warning after merge of the akpm-current tree

On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > fs/jfs/jfs_metapage.c: In function 'force_metapage': > fs/jfs/jfs_metapage.c:714:2: warning: ignoring

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/jfs/jfs_metapage.c: In function 'force_metapage': fs/jfs/jfs_metapage.c:714:2: warning: ignoring return value of 'write_one_page', declared with attribute

linux-next: build warning after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/jfs/jfs_metapage.c: In function 'force_metapage': fs/jfs/jfs_metapage.c:714:2: warning: ignoring return value of 'write_one_page', declared with attribute

  1   2   >