linux-kernel - linux-next: bad commits in the nfs-anna tree

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Fri, 6 Apr 2018 07:43:14 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Anna Schumaker <Anna.Schumaker@...app.com>,
        Trond Myklebust <trondmy@...il.com>,
        NFS Mailing List <linux-nfs@...r.kernel.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: bad commits in the nfs-anna tree

Hi all,

It looks like part of Linus' tree has been rebased into the nfs-anna tree ... commits

  4c8936622a01 ("btrfs: use kvzalloc to allocate btrfs_fs_info")
to
  8f1cd0ae48f5 ("Linux 4.16-rc4")

in the nfs-anna tree are the same as commits

  a8fd1f717493 ("btrfs: use kvzalloc to allocate btrfs_fs_info")
to
  661e50bc8532 ("Linux 4.16-rc4")

I can't use the nfs-anna tree as it is, please fis it up.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped