Subject: Re: [PATCHv8 00/12] nvme: In-band authentication support
To:     Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>
Cc:     Keith Busch <keith.busch@wdc.com>, linux-nvme@lists.infradead.org,
        linux-crypto@vger.kernel.org
References: <20211202152358.60116-1-hare@suse.de>
 <20211213080853.GA21223@lst.de>
 <9853d36a-036c-7f2b-5fb4-b3fb4bae473f@suse.de>
From:   Sagi Grimberg <sagi@grimberg.me>
Message-ID: <4328e4f0-9674-9362-4ed5-89ec7edba4a2@grimberg.me>
Date:   Mon, 13 Dec 2021 11:31:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <9853d36a-036c-7f2b-5fb4-b3fb4bae473f@suse.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk


>> So if we want to make progress on this we need the first 3 patches
>> rewviewed by the crypto maintainers.  In fact I'd prefer to get them
>> merged through the crypto tree as well, and would make sure we have
>> a branch that pulls them in for the nvme changes.  I'll try to find
>> some time to review the nvme bits as well.
>>
> That is _actually_ being addressed already.
> Nicolai Stange send a patchset for ephemeral keys, FFDHE support, and 
> FIPS-related thingies for the in-kernel DH crypto implementation 
> (https://lore.kernel.org/linux-crypto/20211209090358.28231-1-nstange@suse.de/). 
> 
> This obsoletes my preliminary patches, and I have ported my patchset to 
> run on top of those.
> 
> Question is how to continue from here; I can easily rebase my patchset 
> and send it relative to Nicolais patches. But then we'll be bound to the 
> acceptance of those patches, so I'm not quite sure if that's the best 
> way to proceed.

Don't know if we have a choice here... What is the alternative you are
proposing?