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
| ||
|
Date: Sun, 9 Dec 2018 20:55:51 -0700 From: Jens Axboe <axboe@...nel.dk> To: Stephen Rothwell <sfr@...b.auug.org.au>, Alasdair G Kergon <agk@...hat.com>, Mike Snitzer <snitzer@...hat.com> Cc: Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: linux-next: manual merge of the device-mapper tree with the block tree On 12/9/18 8:43 PM, Stephen Rothwell wrote: > Hi all, > > It appears that there are a series of shared patches between the block > and device-mapper trees that are not the same commits. I assume that the > block tree has been rebased, while the device mapper tree that was based > (or includes) part of the block tree has not bee rebased (yet). Yep that's my fault, due to a stupid mistake I had to rebase the block tree. Didn't realize that Mike's tree was based on it. Mike, would it be a big issue for you to rebase the dm tree? -- Jens Axboe
Powered by blists - more mailing lists