All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Tadeusz Struk <tadeusz.struk@intel.com>, herbert@gondor.apana.org.au
Cc: john.griffin@intel.com, bruce.w.allan@intel.com,
	karen.xiang@intel.com, pingchaox.yang@intel.com,
	bo.cui@intel.com, davem@davemloft.net, qat-linux@intel.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	dwmw2@infradead.org, ben@decadent.org.uk
Subject: Re: [RFC][PATCH 4/4] crypto: Updated makefiles to add QAT
Date: Tue, 03 Jun 2014 12:16:22 -0700	[thread overview]
Message-ID: <538E1F06.8070300@infradead.org> (raw)
In-Reply-To: <20140603182400.GA18752@gitlad.jf.intel.com>

On 06/03/2014 11:24 AM, Tadeusz Struk wrote:
> Update to makefiles etc.
> Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
> ---
>  Documentation/ioctl/ioctl-number.txt | 1 +
>  MAINTAINERS                          | 6 ++++++
>  drivers/crypto/Kconfig               | 1 +
>  drivers/crypto/Makefile              | 1 +
>  firmware/Makefile                    | 1 +
>  5 files changed, 10 insertions(+)
> 

> diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
> index f066fa2..1f20814 100644
> --- a/drivers/crypto/Kconfig
> +++ b/drivers/crypto/Kconfig
> @@ -418,4 +418,5 @@ config CRYPTO_DEV_MXS_DCP
>  	  To compile this driver as a module, choose M here: the module
>  	  will be called mxs-dcp.
>  
> +source "drivers/crypto/qat/Kconfig"

Missing that file ^^^^^^^^^^^^^^^^^^^

>  endif # CRYPTO_HW


-- 
~Randy

  reply	other threads:[~2014-06-03 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 18:24 [RFC][PATCH 4/4] crypto: Updated makefiles to add QAT Tadeusz Struk
2014-06-03 19:16 ` Randy Dunlap [this message]
2014-06-03 20:47   ` Tadeusz Struk

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=538E1F06.8070300@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=ben@decadent.org.uk \
    --cc=bo.cui@intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=dwmw2@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.griffin@intel.com \
    --cc=karen.xiang@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pingchaox.yang@intel.com \
    --cc=qat-linux@intel.com \
    --cc=tadeusz.struk@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.