From: Roman Gushchin <guro@fb.com>
To: Yang Li <pku.leo@gmail.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
open list <linux-kernel@vger.kernel.org>,
<andreas.schaufler@gmx.de>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Mike Kravetz <mike.kravetz@oracle.com>,
Michal Hocko <mhocko@kernel.org>, Rik van Riel <riel@surriel.com>,
<js1304@gmail.com>, <lkft-triage@lists.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'
Date: Fri, 10 Apr 2020 09:19:23 -0700 [thread overview]
Message-ID: <20200410161923.GB14685@carbon.lan> (raw)
In-Reply-To: <CADRPPNTSOJsz3kihZ3vXK0i6zWpUY_C36GxqmMO6ehACPT=aBg@mail.gmail.com>
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@fb.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!
prev parent reply other threads:[~2020-04-10 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 14:18 mm/hugetlb.c:5580:3: error: implicit declaration of function 'for_each_mem_pfn_range'; did you mean 'for_each_mem_range' Naresh Kamboju
2020-04-06 17:25 ` Roman Gushchin
2020-04-09 22:06 ` Yang Li
2020-04-10 16:19 ` Roman Gushchin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200410161923.GB14685@carbon.lan \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=andreas.schaufler@gmx.de \
--cc=js1304@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=naresh.kamboju@linaro.org \
--cc=pku.leo@gmail.com \
--cc=riel@surriel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).