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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210625163701.407a2561@canb.auug.org.au>
Date:   Fri, 25 Jun 2021 16:37:01 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Gavin Shan <gshan@...hat.com>,
        David Hildenbrand <david@...hat.com>,
        Alexander Duyck <alexanderduyck@...com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the akpm-current tree

Hi all,

On Fri, 25 Jun 2021 16:34:42 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Fri, 25 Jun 2021 16:28:15 +1000 Gavin Shan <gshan@...hat.com> wrote:
> >
> > On 6/24/21 7:43 PM, Stephen Rothwell wrote:  
> > > Hi all,
> > > 
> > > After merging the akpm-current tree, today's linux-next build (powerpc
> > > ppc64_defconfig) failed like this:
> > > 
> > > mm/page_reporting.c:14:37: error: initializer element is not constant
> > >     14 | unsigned int page_reporting_order = pageblock_order;
> > >        |                                     ^~~~~~~~~~~~~~~
> > > 
> > > Caused by commit
> > > 
> > >    223f64d9e679 ("mm/page_reporting: export reporting order as module parameter")
> > > 
> > > pageblock_order is defined to be various things depending on CONFIG_
> > > symbols.
> > > 
> > > I have reverted that commit (and the following three) for today.
> > >     
> > 
> > Yes, Please drop this series for now.
> > 
> > The v3 was applied and caused the build error. Actually, we need
> > v5, which was posted couple of hours ago.
> > 
> >     v5: https://lkml.org/lkml/2021/6/24/1137  
> 
> Which version is in today's mmotm?

hmm, looks like v4.  So do I drop these again today?

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped