Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH] nvme: tcp: depends on CRYPTO_HASH2 for nvme-tcp
Date: Fri, 12 Jul 2019 02:08:51 +0900	[thread overview]
Message-ID: <20190711170851.GA17328@minwoo-desktop> (raw)
In-Reply-To: <d67b7a73-0061-202c-457d-93bc4cd06122@grimberg.me>

Hi Sagi,

Thanks for your review on this.

On 19-07-11 09:05:28, Sagi Grimberg wrote:
> Hi Minwoo,
> 
> > The tcp host module is now taking those APIs from crypto ahash:
> > 	(1) crypto_ahash_final()
> > 	(2) crypto_ahash_digest()
> > 	(3) crypto_alloc_ahash()
> > 
> > nvme-tcp should depends on CRYPTO_HASH2.
> 
> It actually should depend on CRYPTO_CRC32C because
> it needs CRC32C.

Okay.  That looks right for this commit's goal..

> > 
> > Cc: Christoph Hellwig <hch at lst.de>
> > Cc: Keith Busch <kbusch at kernel.org>
> > Cc: Sagi Grimberg <sagi at grimberg.me>
> > Cc: Jens Axboe <axboe at fb.com>
> > Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
> > ---
> >   drivers/nvme/host/Kconfig | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/nvme/host/Kconfig b/drivers/nvme/host/Kconfig
> > index ec43ac9199e2..711d3ea5143f 100644
> > --- a/drivers/nvme/host/Kconfig
> > +++ b/drivers/nvme/host/Kconfig
> > @@ -63,6 +63,7 @@ config NVME_TCP
> >   	tristate "NVM Express over Fabrics TCP host driver"
> >   	depends on INET
> >   	depends on BLK_DEV_NVME
> > +	depends on CRYPTO_HASH2
> 
> Lets make it select instead.

Oh, That would be much easier to use them.  Will prepare updated patch
soon.

Thanks,

      reply	other threads:[~2019-07-11 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11 15:13 [PATCH] nvme: tcp: depends on CRYPTO_HASH2 for nvme-tcp Minwoo Im
2019-07-11 16:05 ` Sagi Grimberg
2019-07-11 17:08   ` Minwoo Im [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190711170851.GA17328@minwoo-desktop \
    --to=minwoo.im.dev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox