linux-kernel - linux-next: upcoming conflict between the target-updates and target-bva trees

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

Message-ID: <20170602133928.2afa3e7a@canb.auug.org.au>
Date:   Fri, 2 Jun 2017 13:39:28 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     "Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
        Bart Van Assche <bart.vanassche@...il.com>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: upcoming conflict between the target-updates and
 target-bva trees

Hi all,

Last night the tagret-bva tree was rebased on top of the target-updates
tree.  Just now, part of the target-updates tree has been rewritten.
So now I expect to get conflict(s) when I merge these trees since the
commits in the target-updates tree are no longer the same as those that
the target-bva tree was rebased on top of.

Please take a little time to sort out your development process.

-- 
Cheers,
Stephen Rothwell