linux-kernel - Re: linux-next: interesting merge in the zonefs 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CY4PR04MB375191BC8B3ED61678D16CB2E7790@CY4PR04MB3751.namprd04.prod.outlook.com>
Date:   Wed, 22 Jul 2020 14:19:44 +0000
From:   Damien Le Moal <Damien.LeMoal@....com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
CC:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jens Axboe <axboe@...nel.dk>
Subject: Re: linux-next: interesting merge in the zonefs tree

On 2020/07/22 22:58, Stephen Rothwell wrote:
> Hi all,
> 
> It looks an old version of the block tree has been merged into the
> zonefs tree.  Is that deliberate?  Other trees should not be merged unless
> they are guaranteed not to be rebased (which is what has happened here).
> 

I must have done something wrong. Patches for zonefs for 5.9 depend on patches
in Jens tree. So I merged Jens for-next tree into zonefs for-5.9 branch as a
base for the new patches. zonefs for-next branch should contain the same, but I
may have screwed up somewhere... Let me check.


-- 
Damien Le Moal
Western Digital Research