From: Ian Kent <firstname.lastname@example.org> To: Randy Dunlap <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, Al Viro <email@example.com> Subject: Re: mmotm 2018-05-17-16-26 uploaded (autofs) Date: Fri, 18 May 2018 11:50:19 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 18/05/18 08:21, Randy Dunlap wrote: > On 05/17/2018 04:26 PM, firstname.lastname@example.org wrote: >> The mm-of-the-moment snapshot 2018-05-17-16-26 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 (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. > > > on x86_64: with (randconfig): > CONFIG_AUTOFS_FS=y > CONFIG_AUTOFS4_FS=y Oh right, I need to make these exclusive. I seem to remember trying to do that along the way, can't remember why I didn't do it in the end. Any suggestions about potential problems when doing it? Thanks, Ian
next prev parent reply other threads:[~2018-05-18 3:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-17 23:26 mmotm 2018-05-17-16-26 uploaded akpm 2018-05-18 0:21 ` mmotm 2018-05-17-16-26 uploaded (autofs) Randy Dunlap 2018-05-18 3:50 ` Ian Kent [this message] 2018-05-18 4:23 ` Randy Dunlap 2018-05-18 4:38 ` Ian Kent 2018-05-18 6:09 ` Ian Kent 2018-05-18 16:22 ` Randy Dunlap 2018-05-21 0:43 ` Ian Kent 2018-05-21 0:49 ` Ian Kent
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: mmotm 2018-05-17-16-26 uploaded (autofs)' \ /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
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).