[forgot to add netdev] On 05/25/2018 04:14 PM, Randy Dunlap wrote: > On 05/25/2018 02:52 PM, a...@linux-foundation.org wrote: >> The mm-of-the-moment snapshot 2018-05-25-14-52 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. > > on x86_64: > # CONFIG_OF is not set > > CC drivers/net/ethernet/ti/davinci_cpdma.o > ../drivers/net/ethernet/ti/davinci_mdio.c: In function 'davinci_mdio_probe': > ../drivers/net/ethernet/ti/davinci_mdio.c:380:3: error: implicit declaration > of function 'davinci_mdio_probe_dt' [-Werror=implicit-function-declaration] > ret = davinci_mdio_probe_dt(&data->pdata, pdev); > > > >> >> You will need quilt to apply these patches to the latest Linus release (4.x >> or 4.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 git tree which contains the memory management portion of this tree is >> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git >> by Michal Hocko. It contains the patches which are between the >> "#NEXT_PATCHES_START mm" and "#NEXT_PATCHES_END" markers, from the series >> file, http://www.ozlabs.org/~akpm/mmotm/series. >> >> >> 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. >> >> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/ >> >> To develop on top of mmotm git: >> >> $ git remote add mmotm >> git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git >> $ git remote update mmotm >> $ git checkout -b topic mmotm/master >> <make changes, commit> >> $ git send-email mmotm/master.. [...] >> >> To rebase a branch with older patches to a new mmotm release: >> >> $ git remote update mmotm >> $ git rebase --onto mmotm/master <topic base> topic >> >> >> >> >> 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 available at >> >> http://git.cmpxchg.org/cgit.cgi/linux-mmots.git/ >> >> and use of this tree is similar to >> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/, described above. >> >> >> This mmotm tree contains the following patches against 4.17-rc6: >> (patches marked "*" will be included in linux-next) >> > >
-- ~Randy
