linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	linux-crypto@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	devicetree@vger.kernel.org, Tawfik Bayouk <tawfik@marvell.com>,
	Lior Amsalem <alior@marvell.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Eran Ben-Avi <benavi@marvell.com>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Arnaud Ebalard <arno@natisbad.org>
Subject: Re: [PATCH v2 2/7] crypto: add new driver for Marvell CESA
Date: Mon, 4 May 2015 15:26:47 +0200	[thread overview]
Message-ID: <20150504152647.7bd79751@bbrezillon> (raw)
In-Reply-To: <1430742426-21202-3-git-send-email-boris.brezillon@free-electrons.com>

On Mon,  4 May 2015 14:27:01 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:

[...]

> +
> +#include "cesa.h"
> +
> +static int allhwsupport = !IS_ENABLED(CRYPTO_DEV_MV_CESA);

s/CRYPTO_DEV_MV_CESA/CONFIG_CRYPTO_DEV_MV_CESA/


-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2015-05-04 13:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 12:26 [PATCH v2 0/2] crypto: add a new driver for Marvell CESA Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 1/7] crypto: mv_cesa: request registers memory region Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 2/7] crypto: add new driver for Marvell CESA Boris Brezillon
2015-05-04 13:26   ` Boris Brezillon [this message]
2015-05-07  3:01   ` Herbert Xu
2015-05-07  7:18     ` Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 3/7] crypto: marvell/CESA: update DT bindings documentation Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 4/7] ARM: marvell/dt: add crypto node to armada-xp SoC Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 5/7] ARM: marvell/dt: add crypto node to armada-xp-gp board Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 6/7] ARM: marvell/dt: add crypto node to armada 370 SoC Boris Brezillon
2015-05-04 12:27 ` [PATCH v2 7/7] ARM: marvell/dt: add crypto node to kirkwood SoC Boris Brezillon

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=20150504152647.7bd79751@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=alior@marvell.com \
    --cc=andrew@lunn.ch \
    --cc=arno@natisbad.org \
    --cc=benavi@marvell.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nadavh@marvell.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=tawfik@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).