Re: mmotm 2013-07-18-16-40 uploaded
On Fri 19-07-13 15:58:12, Johannes Weiner wrote: > On Fri, Jul 19, 2013 at 11:17:44AM -0700, Andrew Morton wrote: > > On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner > > wrote: > > > > > > >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/?p=linux-mmotm.git;a=summary > > > > > > > > > >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 > > > > > > > > > > $ 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 > > > > > > Andrew, that workflow is actually meant for > > > http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree > > > (i.e. the git remote add mmotm does not make much > > > sense). Michal's tree is append-only, so all this precision-rebasing > > > is unnecessary. > > > > Gee, I haven't looked at that text in a while... > > > > Could you guys please check it, propose any fixes we should make? > > > > > > > > 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 (3.x > > or 3.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--mm-dd-hh-mm-ss. Both contain the string -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 > > ^^^ >on top of the latest >Linus release > > maybe? Yes and also a mention that the lastest since-X.Y branch should be used. [...] > Michal started his mm.git to have a stable memory management > development base, yet here is a long section on how to work with the > much more awkward mmotm.git. So I wonder if this whole section on how > to develop against mmotm.git should be removed and only a reference to > where it could be found left in. > > However, I have actually no idea what people use as an mm development > base these days... I guess Glauber was using it for his shrinker patchset. Few other random people have asked about the tree in the past but I have no idea how many people use the tree, to be honest. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri 19-07-13 11:17:44, Andrew Morton wrote: [...] > 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. Well, I think "It contains the patches which are mm related." would be more precise because I am taking also patches which are outside mm (e.g. shrinkers section currently). -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri 19-07-13 11:17:44, Andrew Morton wrote: [...] 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. Well, I think It contains the patches which are mm related. would be more precise because I am taking also patches which are outside mm (e.g. shrinkers section currently). -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri 19-07-13 15:58:12, Johannes Weiner wrote: On Fri, Jul 19, 2013 at 11:17:44AM -0700, Andrew Morton wrote: On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner han...@cmpxchg.org wrote: 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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. Gee, I haven't looked at that text in a while... Could you guys please check it, propose any fixes we should make? 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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 ^^^ on top of the latest Linus release maybe? Yes and also a mention that the lastest since-X.Y branch should be used. [...] Michal started his mm.git to have a stable memory management development base, yet here is a long section on how to work with the much more awkward mmotm.git. So I wonder if this whole section on how to develop against mmotm.git should be removed and only a reference to where it could be found left in. However, I have actually no idea what people use as an mm development base these days... I guess Glauber was using it for his shrinker patchset. Few other random people have asked about the tree in the past but I have no idea how many people use the tree, to be honest. -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Mon, Jul 22, 2013 at 08:42:20PM +0800, Paul Bolle wrote: > On 07/20/2013 02:00 AM, Johannes Weiner wrote: > >On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: > >>On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: > >>>The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x > >>>or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary > >>> > >>>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 > >>> > >>> $ 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 > >Andrew, that workflow is actually meant for > >http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree > >(i.e. the git remote add mmotm does not make much > >sense). Michal's tree is append-only, so all this precision-rebasing > >is unnecessary. > > > >>The -mm tree is > >>git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or > >>linux-next -mm branch? > >It depends what you want for the base. What's in linux-next is based > >on linux-next, so the latest and greatest. > > > >Michal's -mm tree is based on the latest Linus release, and so more > >stable. Or at least the craziness is contained to mm stuff. > > -mm branch against linux-next is newer than master branch against > linux-next. Michal's -mm tree is newer than Linus's tree or older? It's based on the latest release, so newer than the latest release and usually older than what's currently in Linus's master branch. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Mon, Jul 22, 2013 at 08:15:50PM +0800, Paul Bolle wrote: > On 07/20/2013 02:00 AM, Johannes Weiner wrote: > >On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: > >>On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: > >>>The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x > >>>or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary > >>> > >>>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 > >>> > >>> $ 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 > >Andrew, that workflow is actually meant for > >http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree > >(i.e. the git remote add mmotm does not make much > >sense). Michal's tree is append-only, so all this precision-rebasing > >is unnecessary. > > > >>The -mm tree is > >>git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or > >>linux-next -mm branch? > >It depends what you want for the base. What's in linux-next is based > >on linux-next, so the latest and greatest. > > But Andrew has his own queue which is the most latest one before > merged into linux-next. How can developer works against his queue? By using either the quilt series from http://www.ozlabs.org/~akpm/mmotm/ or the master branch from http://git.cmpxchg.org/cgit/linux-mmotm.git/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 $ 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -mm branch against linux-next is newer than master branch against linux-next. Michal's -mm tree is newer than Linus's tree or older? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 $ 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. But Andrew has his own queue which is the most latest one before merged into linux-next. How can developer works against his queue? Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. But Andrew has his own queue which is the most latest one before merged into linux-next. How can developer works against his queue? Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -mm branch against linux-next is newer than master branch against linux-next. Michal's -mm tree is newer than Linus's tree or older? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Mon, Jul 22, 2013 at 08:15:50PM +0800, Paul Bolle wrote: On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. But Andrew has his own queue which is the most latest one before merged into linux-next. How can developer works against his queue? By using either the quilt series from http://www.ozlabs.org/~akpm/mmotm/ or the master branch from http://git.cmpxchg.org/cgit/linux-mmotm.git/ -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Mon, Jul 22, 2013 at 08:42:20PM +0800, Paul Bolle wrote: On 07/20/2013 02:00 AM, Johannes Weiner wrote: On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -mm branch against linux-next is newer than master branch against linux-next. Michal's -mm tree is newer than Linus's tree or older? It's based on the latest release, so newer than the latest release and usually older than what's currently in Linus's master branch. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri, Jul 19, 2013 at 11:17:44AM -0700, Andrew Morton wrote: > On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner wrote: > > > > >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/?p=linux-mmotm.git;a=summary > > > > > > > >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 > > > > > > > > $ 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 > > > > Andrew, that workflow is actually meant for > > http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree > > (i.e. the git remote add mmotm does not make much > > sense). Michal's tree is append-only, so all this precision-rebasing > > is unnecessary. > > Gee, I haven't looked at that text in a while... > > Could you guys please check it, propose any fixes we should make? > > > > 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 (3.x > or 3.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--mm-dd-hh-mm-ss. Both contain the string -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 ^^^ on top of the latest Linus release maybe? > 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/?p=linux-mmotm.git;a=summary > > To develop on top of mmotm git: > > $ git remote add mmotm > git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git git://git.cmpxchg.org/linux-mmotm.git > $ git remote update mmotm > $ git checkout -b topic mmotm/master > > $ 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 Michal started his mm.git to have a stable memory management development base, yet here is a long section on how to work with the much more awkward mmotm.git. So I wonder if this whole section on how to develop against mmotm.git should be removed and only a reference to where it could be found left in. However, I have actually no idea what people use as an mm development base these days... I know I base smaller things on the latest mmotm.git and send it out fairly quickly before even having to deal with rebasing and tracking changes in there. Long term stuff I just base on the latest Linus release (suboptimal, I know). Michal? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner wrote: > > >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/?p=linux-mmotm.git;a=summary > > > > > >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 > > > > > > $ 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 > > Andrew, that workflow is actually meant for > http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree > (i.e. the git remote add mmotm does not make much > sense). Michal's tree is append-only, so all this precision-rebasing > is unnecessary. Gee, I haven't looked at that text in a while... Could you guys please check it, propose any fixes we should make? 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 $ 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 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/?p=linux-mmots.git;a=summary and use of this tree is similar to http://git.cmpxchg.org/?p=linux-mmotm.git, described above. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: > On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: > >The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x > >or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary > > > >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 > > > > $ 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. > The -mm tree is > git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or > linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Thu, Jul 18, 2013 at 11:32:27PM -0400, Paul Bolle wrote: On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? It depends what you want for the base. What's in linux-next is based on linux-next, so the latest and greatest. Michal's -mm tree is based on the latest Linus release, and so more stable. Or at least the craziness is contained to mm stuff. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner han...@cmpxchg.org wrote: 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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. Gee, I haven't looked at that text in a while... Could you guys please check it, propose any fixes we should make? 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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/?p=linux-mmots.git;a=summary and use of this tree is similar to http://git.cmpxchg.org/?p=linux-mmotm.git, described above. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On Fri, Jul 19, 2013 at 11:17:44AM -0700, Andrew Morton wrote: On Fri, 19 Jul 2013 14:00:35 -0400 Johannes Weiner han...@cmpxchg.org wrote: 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/?p=linux-mmotm.git;a=summary 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 Andrew, that workflow is actually meant for http://git.cmpxchg.org/?p=linux-mmotm.git;a=summary, not Michal's tree (i.e. the git remote add mmotm michal's tree does not make much sense). Michal's tree is append-only, so all this precision-rebasing is unnecessary. Gee, I haven't looked at that text in a while... Could you guys please check it, propose any fixes we should make? 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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 ^^^ on top of the latest Linus release maybe? 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/?p=linux-mmotm.git;a=summary To develop on top of mmotm git: $ git remote add mmotm git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git git://git.cmpxchg.org/linux-mmotm.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 Michal started his mm.git to have a stable memory management development base, yet here is a long section on how to work with the much more awkward mmotm.git. So I wonder if this whole section on how to develop against mmotm.git should be removed and only a reference to where it could be found left in. However, I have actually no idea what people use as an mm development base these days... I know I base smaller things on the latest mmotm.git and send it out fairly quickly before even having to deal with rebasing and tracking changes in there. Long term stuff I just base on the latest Linus release (suboptimal, I know). Michal? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: mmotm 2013-07-18-16-40 uploaded
On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 $ 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 Hi Andrew, The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? 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/?p=linux-mmots.git;a=summary and use of this tree is similar to http://git.cmpxchg.org/?p=linux-mmotm.git, described above. This mmotm tree contains the following patches against 3.11-rc1: (patches marked "*" will be included in linux-next) origin.patch * revert-include-linux-smph-on_each_cpu-switch-back-to-a-macro.patch arch-alpha-kernel-systblss-remove-debug-check.patch i-need-old-gcc.patch * mm-mempolicy-fix-mbind_range-vma_adjust-interaction.patch * ocfs2-refcounttree-add-the-missing-null-check-of-the-return-value-of-find_or_create_page.patch * ocfs2-refcounttree-add-the-missing-null-check-of-the-return-value-of-find_or_create_page-fix.patch * dmi_scan-add-comments-on-dmi_present-and-the-loop-in-dmi_scan_machine.patch * maintainers-dynamic-debug-jasons-not-there.patch * gitignore-ignore-lz4-files.patch * rapidio-fix-use-after-free-in-rio_unregister_scan.patch * mm-sched-numa-fix-numa-balancing-when-sched_debug.patch * arch-x86-platform-ce4100-ce4100c-include-rebooth.patch * mm-swapc-clear-pageactive-before-adding-pages-onto-unevictable-list.patch * thp-mm-avoid-pageunevictable-on-active-inactive-lru-lists.patch * drivers-thermal-x86_pkg_temp_thermalc-fix-lockup-of-cpu_down.patch * mm-zbud-fix-condition-check-on-allocation-size.patch * documentation-development-process-update-mm-and-next-urls.patch * printk-move-to-separate-directory-for-easier-modification.patch * printk-add-console_cmdlineh.patch * printk-move-braille-console-support-into-separate-braille-files.patch * printk-use-pointer-for-console_cmdline-indexing.patch * printk-rename-struct-log-to-struct-printk_log.patch * x86-make-mem=-option-to-work-for-efi-platform.patch * drivers-pcmcia-pd6729c-convert-to-module_pci_driver.patch * drivers-pcmcia-yenta_socketc-convert-to-module_pci_driver.patch * drm-fb-helper-dont-sleep-for-screen-unblank-when-an-oopps-is-in-progress.patch * drm-cirrus-correct-register-values-for-16bpp.patch * drm-nouveau-make-vga_switcheroo-code-depend-on-vga_switcheroo.patch * drivers-video-acornfbc-remove-dead-code.patch * cyber2000fb-avoid-palette-corruption-at-higher-clocks.patch * include-linux-interrupth-add-dummy-irq_set_irq_wake-for-generic_hardirqs.patch * hrtimer-one-more-expiry-time-overflow-check-in-hrtimer_interrupt.patch * drivers-infiniband-core-cmc-convert-to-using-idr_alloc_cyclic.patch * drivers-mtd-chips-gen_probec-refactor-call-to-request_module.patch * drivers-net-ethernet-ibm-ehea-ehea_mainc-add-alias-entry-for-portn-properties.patch * misdn-add-support-for-group-membership-check.patch * drivers-atm-he-convert-to-module_pci_driver.patch
Re: mmotm 2013-07-18-16-40 uploaded
On 07/18/2013 07:41 PM, a...@linux-foundation.org wrote: The mm-of-the-moment snapshot 2013-07-18-16-40 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 (3.x or 3.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--mm-dd-hh-mm-ss. Both contain the string -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/?p=linux-mmotm.git;a=summary 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 Hi Andrew, The -mm tree is git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git or linux-next -mm branch? 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/?p=linux-mmots.git;a=summary and use of this tree is similar to http://git.cmpxchg.org/?p=linux-mmotm.git, described above. This mmotm tree contains the following patches against 3.11-rc1: (patches marked * will be included in linux-next) origin.patch * revert-include-linux-smph-on_each_cpu-switch-back-to-a-macro.patch arch-alpha-kernel-systblss-remove-debug-check.patch i-need-old-gcc.patch * mm-mempolicy-fix-mbind_range-vma_adjust-interaction.patch * ocfs2-refcounttree-add-the-missing-null-check-of-the-return-value-of-find_or_create_page.patch * ocfs2-refcounttree-add-the-missing-null-check-of-the-return-value-of-find_or_create_page-fix.patch * dmi_scan-add-comments-on-dmi_present-and-the-loop-in-dmi_scan_machine.patch * maintainers-dynamic-debug-jasons-not-there.patch * gitignore-ignore-lz4-files.patch * rapidio-fix-use-after-free-in-rio_unregister_scan.patch * mm-sched-numa-fix-numa-balancing-when-sched_debug.patch * arch-x86-platform-ce4100-ce4100c-include-rebooth.patch * mm-swapc-clear-pageactive-before-adding-pages-onto-unevictable-list.patch * thp-mm-avoid-pageunevictable-on-active-inactive-lru-lists.patch * drivers-thermal-x86_pkg_temp_thermalc-fix-lockup-of-cpu_down.patch * mm-zbud-fix-condition-check-on-allocation-size.patch * documentation-development-process-update-mm-and-next-urls.patch * printk-move-to-separate-directory-for-easier-modification.patch * printk-add-console_cmdlineh.patch * printk-move-braille-console-support-into-separate-braille-files.patch * printk-use-pointer-for-console_cmdline-indexing.patch * printk-rename-struct-log-to-struct-printk_log.patch * x86-make-mem=-option-to-work-for-efi-platform.patch * drivers-pcmcia-pd6729c-convert-to-module_pci_driver.patch * drivers-pcmcia-yenta_socketc-convert-to-module_pci_driver.patch * drm-fb-helper-dont-sleep-for-screen-unblank-when-an-oopps-is-in-progress.patch * drm-cirrus-correct-register-values-for-16bpp.patch * drm-nouveau-make-vga_switcheroo-code-depend-on-vga_switcheroo.patch * drivers-video-acornfbc-remove-dead-code.patch * cyber2000fb-avoid-palette-corruption-at-higher-clocks.patch * include-linux-interrupth-add-dummy-irq_set_irq_wake-for-generic_hardirqs.patch * hrtimer-one-more-expiry-time-overflow-check-in-hrtimer_interrupt.patch * drivers-infiniband-core-cmc-convert-to-using-idr_alloc_cyclic.patch * drivers-mtd-chips-gen_probec-refactor-call-to-request_module.patch * drivers-net-ethernet-ibm-ehea-ehea_mainc-add-alias-entry-for-portn-properties.patch * misdn-add-support-for-group-membership-check.patch *
