linux-kernel - Re: mm/hugetlb.c:5580:3: error: implicit declaration of function 'for_each_mem_pfn_range'; did you mean 'for_each_mem

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Fri, 10 Apr 2020 09:19:23 -0700
From:   Roman Gushchin <guro@...com>
To:     Yang Li <pku.leo@...il.com>
CC:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        open list <linux-kernel@...r.kernel.org>,
        <andreas.schaufler@....de>,
        "Kirill A. Shutemov" <kirill@...temov.name>,
        Mike Kravetz <mike.kravetz@...cle.com>,
        Michal Hocko <mhocko@...nel.org>,
        Rik van Riel <riel@...riel.com>, <js1304@...il.com>,
        <lkft-triage@...ts.linaro.org>
Subject: Re: mm/hugetlb.c:5580:3: error: implicit declaration of function
 'for_each_mem_pfn_range'; did you mean 'for_each_mem_range'

On Thu, Apr 09, 2020 at 05:06:17PM -0500, Yang Li wrote:
> On Mon, Apr 6, 2020 at 12:37 PM Roman Gushchin <guro@...com> wrote:
> >
> > On Mon, Apr 06, 2020 at 07:48:54PM +0530, Naresh Kamboju wrote:
> > > While building Linux-next master for arm beagle board x15 the following
> > > build error was noticed.
> >
> > Hello Naresh!
> >
> > There was a number of cleanups and fixes to the original hugetlb_cma
> > patch, and it looks like some parts were lost.
> > I'm going to gather all changes and resubmit a new version later today.
> > Sorry for the inconvenience.
> 
> Hi Roman,
> 
> I'm still getting this compile issue with linux-next tag
> next-20200409.  If the current patch set is broken, can we remove them
> from the linux-next for now?

Hi Yang!

The correct patch is already picked by Andrew Morton, it just haven't been
propagated to the linux-next tree. It should happen automatically in the
next day or two.

Thanks!