[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPcyv4jSbD16zixV3FRVgsd6nPjctTQ3OLi16ryBj7SB-H30=g@mail.gmail.com>
Date: Fri, 3 Nov 2017 09:04:59 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jan Kara <jack@...e.cz>
Subject: Re: linux-next: build failure after merge of the nvdimm tree
On Fri, Nov 3, 2017 at 12:19 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Dan,
>
> After merging the nvdimm tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> In file included from arch/powerpc/kernel/asm-offsets.c:22:0:
> include/linux/mman.h: In function 'calc_vm_flag_bits':
> include/linux/mman.h:109:48: warning: division by zero [-Wdiv-by-zero]
> ((bit1) <= (bit2) ? ((x) & (bit1)) * ((bit2) / (bit1)) \
> ^
> include/linux/mman.h:133:9: note: in expansion of macro '_calc_vm_trans'
> _calc_vm_trans(flags, MAP_SYNC, VM_SYNC );
> ^
> cc1: all warnings being treated as errors
>
> and more like these ...
>
> Caused by commit
>
> ebd0722a382c ("mm: Define MAP_SYNC and VM_SYNC flags")
>
> Not all architectures use asm-generic/mman.h
>
> I have used the nvdimm tree from next-20171102 for today.
Thanks, Stephen. I included Jan's fix for this issue in today's
version of the libnvdimm-for-next branch.
Powered by blists - more mailing lists