[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220222200907.GA1782741@dhcp-10-100-145-180.wdc.com>
Date: Tue, 22 Feb 2022 12:09:07 -0800
From: Keith Busch <kbusch@...nel.org>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org,
linux-crypto@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org, axboe@...nel.dk, hch@....de,
martin.petersen@...cle.com, colyli@...e.de
Subject: Re: [PATCHv3 06/10] crypto: add rocksoft 64b crc framework
On Tue, Feb 22, 2022 at 11:50:42AM -0800, Eric Biggers wrote:
> On Tue, Feb 22, 2022 at 08:31:40AM -0800, Keith Busch wrote:
> > +config CRYPTO_CRC64_ROCKSOFT
> > + tristate "Rocksoft Model CRC64 algorithm"
> > + depends on CRC64
> > + select CRYPTO_HASH
> > + help
> > + Rocksoft Model CRC64 computation is being cast as a crypto
> > + transform. This allows for faster crc64 transforms to be used
> > + if they are available.
>
> The first sentence of this help text doesn't make sense.
Much of the this patch is a copy from the equivalent T10DIF option,
which says the same as above. I meant to revist these help texts because
they don't make sense to me either. I'll be sure to do that for the next
version.
Powered by blists - more mailing lists