linux-kernel - Re: [GIT PULL] f2fs update for 4.16-rc1

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 3 May 2018 11:49:00 +0200
From:   David Sterba <dsterba@...e.cz>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
        Jaegeuk Kim <jaegeuk@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Yufen Yu <yuyufen@...wei.com>, Tejun Heo <tj@...nel.org>
Subject: Re: [GIT PULL] f2fs update for 4.16-rc1

On Thu, May 03, 2018 at 08:42:59AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 3 Apr 2018 12:29:19 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Ping?
> 
> Ping again ...
> 
> So has Chris gone missing?  Or should I just remove the btrfs tree from linux-next?

As far as btrfs code changes are concerned, they go through my tree. The
other conflicting changes are some cgroup tweaks that have impact on
btrfs but do not affect the development.