linux-kernel - Re: linux-next: manual merge of the block tree with the vfs-idmapping 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: <20230511110750.76a33556@canb.auug.org.au>
Date:   Thu, 11 May 2023 11:07:50 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Jens Axboe <axboe@...nel.dk>
Cc:     Christian Brauner <christian@...uner.io>,
        Seth Forshee <sforshee@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the block tree with the
 vfs-idmapping tree

Hi Jens,

On Wed, 10 May 2023 06:48:39 -0600 Jens Axboe <axboe@...nel.dk> wrote:
>
> Yes, since Linus didn't like the original approach, it was redone
> and that particular patch was originally forgotten and then redone
> without the 'nonblock' variable. So you should just ignore the
> old version, and Christian should just drop that branch from his
> for-next tree as it's dead.

That appears to have been done now, thanks.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped