On Mon, 6 Apr 2020 at 16:13, Naresh Kamboju <naresh.kamboju@xxxxxxxxxx> wrote: > > On Mon, 6 Apr 2020 at 05:16, <akpm@xxxxxxxxxxxxxxxxxxxx> 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) { > ^ > Few more details about build test, CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_CMA is not set Kernel config link, http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/intel-core2-32/lkft/linux-mainline/2591/config Build log, https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=am57xx-evm,label=docker-lkft/743/consoleText > -- > Linaro LKFT > https://lkft.linaro.org