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

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:

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 > >

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. > >

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:

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 > | >

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

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

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; >

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 *,

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,

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

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, >

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

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

Hi Xunlei, On Mon, 15 May 2017 12:02:18 +0800 Xunlei Pang wrote: > > The following patch will fix it, do you want to me to send it out separately? > or help merge it into > fc7d2b44367f ("powerpc/fadump: use the correct VMCOREINFO_NOTE_SIZE for > phdr") directly? Andrew

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

Hi Xunlei, On Mon, 15 May 2017 12:02:18 +0800 Xunlei Pang wrote: > > The following patch will fix it, do you want to me to send it out separately? > or help merge it into > fc7d2b44367f ("powerpc/fadump: use the correct VMCOREINFO_NOTE_SIZE for > phdr") directly? Andrew normally takes these

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

On 05/15/2017 at 09:56 AM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > In file included from include/asm-generic/bug.h:15:0, > from arch/arm/include/asm/bug.h:59, >

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

On 05/15/2017 at 09:56 AM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > In file included from include/asm-generic/bug.h:15:0, > from arch/arm/include/asm/bug.h:59, >

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

Hi Andrew, On Wed, 9 Nov 2016 13:21:53 -0800 Andrew Morton wrote: > > On Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > > > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > > Hi Stephen, > > > Hi Andrew, > > > > > >

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

Hi Andrew, On Wed, 9 Nov 2016 13:21:53 -0800 Andrew Morton wrote: > > On Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > > > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > > Hi Stephen, > > > Hi Andrew, > > > > > > After merging the akpm-current tree, today's

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

On Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > Hi Stephen, > > 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 Wed, 9 Nov 2016 15:18:24 +0800 Huang Shijie wrote: > On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: > Hi Stephen, > > 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 Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: Hi Stephen, > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/hugetlb.c:1166:21: warning: 'alloc_gigantic_page' defined but not used >

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

On Wed, Nov 09, 2016 at 03:10:06PM +1100, Stephen Rothwell wrote: Hi Stephen, > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > mm/hugetlb.c:1166:21: warning: 'alloc_gigantic_page' defined but not used >

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

On Thu, Jun 23, 2016 at 04:53:21PM +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig and x86_64 allmodconfig) produced this warning: > I asked that Andrew drop the patch series that introduced this problem.

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

On Thu, Jun 23, 2016 at 04:53:21PM +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (powerpc > ppc64_defconfig and x86_64 allmodconfig) produced this warning: > I asked that Andrew drop the patch series that introduced this problem.

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

On Fri, 27 May 2016 13:07:10 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > mm/oom_kill.c: In function '__oom_reap_task': > mm/oom_kill.c:537:2: warning:

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

On Fri, 27 May 2016 13:07:10 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > mm/oom_kill.c: In function '__oom_reap_task': > mm/oom_kill.c:537:2: warning: 'mm' may be used

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

Hi Josh, On Fri, 29 Apr 2016 09:03:42 -0500 Josh Poimboeuf wrote: > > On Fri, Apr 29, 2016 at 08:32:19AM -0500, Josh Poimboeuf wrote: > > On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote: > > > Hi Andrew, > > > > > > After merging the akpm-current tree,

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

Hi Josh, On Fri, 29 Apr 2016 09:03:42 -0500 Josh Poimboeuf wrote: > > On Fri, Apr 29, 2016 at 08:32:19AM -0500, Josh Poimboeuf wrote: > > On Fri, Apr 29, 2016 at 04:45:43PM +1000, 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 Fri, Apr 29, 2016 at 08:32:19AM -0500, Josh Poimboeuf wrote: > On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > > drivers/scsi/ipr.c: In

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

On Fri, Apr 29, 2016 at 08:32:19AM -0500, Josh Poimboeuf wrote: > On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote: > > Hi Andrew, > > > > After merging the akpm-current tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > > drivers/scsi/ipr.c: In

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

On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/scsi/ipr.c: In function 'ipr_show_device_id': > drivers/scsi/ipr.c:4462:34: warning: format

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

On Fri, Apr 29, 2016 at 04:45:43PM +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/scsi/ipr.c: In function 'ipr_show_device_id': > drivers/scsi/ipr.c:4462:34: warning: format

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

Hi All, On Fri, 29 Apr 2016 16:45:43 +1000 Stephen Rothwell wrote: > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/scsi/ipr.c: In function 'ipr_show_device_id': > drivers/scsi/ipr.c:4462:34:

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

Hi All, On Fri, 29 Apr 2016 16:45:43 +1000 Stephen Rothwell wrote: > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/scsi/ipr.c: In function 'ipr_show_device_id': > drivers/scsi/ipr.c:4462:34: warning: format '%llx'

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

On Thu, 16 Jul 2015 15:26:00 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > lib/genalloc.c: In function 'gen_pool_get': > /scratch/sfr/next/lib/genalloc.c:599:6: warning:

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

On Thu, 16 Jul 2015 15:26:00 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/genalloc.c: In function 'gen_pool_get': /scratch/sfr/next/lib/genalloc.c:599:6:

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

Hello, On Thu, Jun 04, 2015 at 10:29:28PM +1000, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > ./usr/include/linux/userfaultfd.h:14: found __[us]{8,16,32,64} type without > #include >

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

Hello, On Thu, Jun 04, 2015 at 10:29:28PM +1000, Stephen Rothwell wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: ./usr/include/linux/userfaultfd.h:14: found __[us]{8,16,32,64} type without #include

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-02-04 08:48, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > warning: (GDB_SCRIPTS) selects DEBUG_INFO which has unmet direct

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-02-04 08:48, Stephen Rothwell wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: warning: (GDB_SCRIPTS) selects DEBUG_INFO which has unmet direct dependencies

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

On Mon, Jan 19, 2015 at 2:45 AM, Stephen Rothwell wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/eventfd.c: In function 'eventfd_poll': fs/eventfd.c:121:16: warning: unused variable 'flags'

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

On Mon, Jan 19, 2015 at 2:45 AM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/eventfd.c: In function 'eventfd_poll': fs/eventfd.c:121:16: warning: unused variable

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

Stephen Rothwell writes: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) > produced this warning: > > In file included from include/linux/mm.h:52:0, > from mm/gup.c:7: > arch/arm/include/asm/pgtable.h:184:0: warning: "pgd_huge"

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

Stephen Rothwell s...@canb.auug.org.au writes: Hi Andrew, After merging the akpm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: In file included from include/linux/mm.h:52:0, from mm/gup.c:7: arch/arm/include/asm/pgtable.h:184:0: warning:

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

On Fri, 26 Sep 2014 20:42:00 +1000 Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > drivers/of/of_reserved_mem.c: In function 'of_reserved_mem_device_init': >

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

On Fri, 26 Sep 2014 20:42:00 +1000 Stephen Rothwell s...@canb.auug.org.au wrote: Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/of/of_reserved_mem.c: In function 'of_reserved_mem_device_init':

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

On Thu, Jun 19, 2014 at 10:27 PM, Stephen Rothwell wrote: > Hi Andrew, > > After merging the akpm-current tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > Introduced by commit 8d9dfa4b0125 ("initramfs: support initramfs that > is more than 2G"). Grep is your

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

On Thu, Jun 19, 2014 at 10:27 PM, Stephen Rothwell s...@canb.auug.org.au wrote: Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: Introduced by commit 8d9dfa4b0125 (initramfs: support initramfs that is more than 2G). Grep