From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
linux-fsdevel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
mhocko@suse.cz, mm-commits@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: mmotm 2020-04-05-16-45 uploaded
Date: Mon, 6 Apr 2020 16:13:17 +0530 [thread overview]
Message-ID: <CA+G9fYsUsGS6ybozk3A=8aG5VFpF-+DJGNAim4o=Xi9CB43tDA@mail.gmail.com> (raw)
In-Reply-To: <20200405234639.AU1f3x3Xg%akpm@linux-foundation.org>
On Mon, 6 Apr 2020 at 05:16, <akpm@linux-foundation.org> wrote:
>
> The mm-of-the-moment snapshot 2020-04-05-16-45 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
>
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> https://github.com/hnaz/linux-mm
>
> The directory http://www.ozlabs.org/~akpm/mmots/ (mm-of-the-second)
> contains daily snapshots of the -mm tree. It is updated more frequently
> than mmotm, and is untested.
>
> A git copy of this tree is also available at
>
> https://github.com/hnaz/linux-mm
>
>
>
> This mmotm tree contains the following patches against 5.6:
> (patches marked "*" will be included in linux-next)
>
> origin.patch
<>
> * mm-hugetlb-optionally-allocate-gigantic-hugepages-using-cma.patch
> * mm-hugetlb-optionally-allocate-gigantic-hugepages-using-cma-fix.patch
> * mm-hugetlb-optionally-allocate-gigantic-hugepages-using-cma-fix-2.patch
While building Linux-next master for arm beagle board x15 the following
build error was noticed.
mm/hugetlb.c: In function 'hugetlb_cma_reserve':
mm/hugetlb.c:5580:3: error: implicit declaration of function
'for_each_mem_pfn_range'; did you mean 'for_each_mem_range'?
[-Werror=implicit-function-declaration]
for_each_mem_pfn_range(i, nid, &start_pfn, &end_pfn, NULL) {
^~~~~~~~~~~~~~~~~~~~~~
for_each_mem_range
mm/hugetlb.c:5580:62: error: expected ';' before '{' token
for_each_mem_pfn_range(i, nid, &start_pfn, &end_pfn, NULL) {
^
--
Linaro LKFT
https://lkft.linaro.org
next prev parent reply other threads:[~2020-04-06 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:46 mmotm 2020-04-05-16-45 uploaded akpm
2020-04-06 5:53 ` mmotm 2020-04-05-16-45 uploaded (objtool warning) Randy Dunlap
2020-04-07 18:00 ` Josh Poimboeuf
2020-04-06 10:43 ` Naresh Kamboju [this message]
2020-04-06 11:00 ` mmotm 2020-04-05-16-45 uploaded Naresh Kamboju
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='CA+G9fYsUsGS6ybozk3A=8aG5VFpF-+DJGNAim4o=Xi9CB43tDA@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).