All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corentin LABBE <clabbe@baylibre.com>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	fenghua.yu@intel.com, vkoul@kernel.org, dave.jiang@intel.com,
	tony.luck@intel.com, wajdi.k.feghali@intel.com,
	james.guilford@intel.com, kanchana.p.sridhar@intel.com,
	giovanni.cabiddu@intel.com, daniele.alessandrelli@intel.com,
	prabhjot.khurana@intel.com, mgross@linux.intel.com,
	declan.murphy@intel.com, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH 2/3] crypto: ixp4xx - Move driver to drivers/crypto/intel/ixp4xx
Date: Mon, 3 Apr 2023 16:54:14 +0200	[thread overview]
Message-ID: <ZCroljP+zzGVigFi@Red> (raw)
In-Reply-To: <20230328153951.126564-3-tom.zanussi@linux.intel.com>

Le Tue, Mar 28, 2023 at 10:39:50AM -0500, Tom Zanussi a écrit :
> With the growing number of Intel crypto drivers, it makes sense to
> group them all into a single drivers/crypto/intel/ directory.
> 
> Create a separate drivers/crypto/intel/ixp4xx directory and move
> drivers/crypto/ixp4xx_crypto.c to it, along with a new Kconfig and
> Makefile to contain the config and make bits.
> 
> Also add a COMPILE_TEST dependency to CRYPTO_DEV_IXP4XX so it can be
> more easily compile-tested.
> 
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>

Acked-by: Corentin LABBE <clabbe@baylibre.com>

Thanks

  reply	other threads:[~2023-04-03 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 15:39 [PATCH 0/3] crypto: Move Intel crypto drivers to drivers/crypto/intel Tom Zanussi
2023-03-28 15:39 ` [PATCH 1/3] crypto: keembay - Move driver to drivers/crypto/intel/keembay Tom Zanussi
2023-03-31 15:08   ` Alessandrelli, Daniele
2023-03-28 15:39 ` [PATCH 2/3] crypto: ixp4xx - Move driver to drivers/crypto/intel/ixp4xx Tom Zanussi
2023-04-03 14:54   ` Corentin LABBE [this message]
2023-03-28 15:39 ` [PATCH 3/3] crypto: qat - Move driver to drivers/crypto/intel/qat Tom Zanussi
2023-04-06  8:50 ` [PATCH 0/3] crypto: Move Intel crypto drivers to drivers/crypto/intel Herbert Xu

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=ZCroljP+zzGVigFi@Red \
    --to=clabbe@baylibre.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=declan.murphy@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.guilford@intel.com \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=prabhjot.khurana@intel.com \
    --cc=tom.zanussi@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=vkoul@kernel.org \
    --cc=wajdi.k.feghali@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.