LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Gilad Ben-Yossef <gilad@benyossef.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
	<linux-crypto@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] crypto: Add platform dependencies for CRYPTO_DEV_CCREE
Date: Tue, 17 Apr 2018 21:53:49 +0200	[thread overview]
Message-ID: <CAK8P3a0fRZmumK5zLRgqT1iPtn2HgEjg6qyv-PMEaM1Z1W6aDw@mail.gmail.com> (raw)
In-Reply-To: <1523988865-26848-1-git-send-email-geert@linux-m68k.org>

On Tue, Apr 17, 2018 at 8:14 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> The ARM TrustZone CryptoCell is found on ARM SoCs only.  Hence make it
> depend on ARM or ARM64, unless compile-testing.
>
> Drop the dependency on HAS_DMA, as DMA is always available on ARM and
> ARM64 platforms, and doing so will increase compile coverage.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> Is ARM || ARM64 OK?
> Or should this be limited to either ARM or ARM64? Or something else?

ARM || ARM64 seems fine, but don't you need '|| (HAS_DMA && COMPILE_TEST)'?

I assume the HAS_DMA dependency was added to prevent compile
testing to run into a build error.

        Arnd

  reply	other threads:[~2018-04-17 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 18:14 Geert Uytterhoeven
2018-04-17 19:53 ` Arnd Bergmann [this message]
2018-04-18  7:43   ` Geert Uytterhoeven
2018-04-18  4:32 ` Gilad Ben-Yossef
2018-04-18  7:47   ` Geert Uytterhoeven
2018-04-23  7:45     ` Gilad Ben-Yossef
2018-04-23  8:11       ` Geert Uytterhoeven

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=CAK8P3a0fRZmumK5zLRgqT1iPtn2HgEjg6qyv-PMEaM1Z1W6aDw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=geert@linux-m68k.org \
    --cc=gilad@benyossef.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH/RFC] crypto: Add platform dependencies for CRYPTO_DEV_CCREE' \
    /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

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).