linux-kernel - Re: mmotm 2016-02-02-17-08 uploaded

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20160203121646.GE6757@dhcp22.suse.cz>
Date:	Wed, 3 Feb 2016 13:16:46 +0100
From:	Michal Hocko <mhocko@...nel.org>
To:	akpm@...ux-foundation.org
Cc:	mm-commits@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
	linux-next@...r.kernel.org, sfr@...b.auug.org.au,
	broonie@...nel.org
Subject: Re: mmotm 2016-02-02-17-08 uploaded


On Tue 02-02-16 17:09:03, 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.

JFYI DAX changes are really hard to track properly because there are
some changes coming from different trees, the code changes permanently
and it is really hard to see what is the current base so I have skipped
those fixes which depend on the code which is outside of mmotm patches +
linus tree.

If you want to develop for DAX or something that might clash there
please use linux-next instead.
-- 
Michal Hocko
SUSE Labs