linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Richard Weinberger <richard@nod.at>, linux-kernel@vger.kernel.org
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Lee Jones <lee.jones@linaro.org>,
	Kieran Bingham <kieranbingham@gmail.com>,
	Pankaj Dev <pankaj.dev@st.com>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH 05/22] hw_random: Fix dependencies for !HAS_IOMEM archs
Date: Tue, 26 Jan 2016 09:58:51 +0000	[thread overview]
Message-ID: <56A7435B.5000405@linaro.org> (raw)
In-Reply-To: <1453760661-1444-6-git-send-email-richard@nod.at>

On 25/01/16 22:24, Richard Weinberger wrote:
> Not every arch has io memory.
> So, unbreak the build by fixing the dependencies.
>
> Signed-off-by: Richard Weinberger <richard@nod.at>

Reviewed-by: Daniel Thompson <daniel.thompson@linaro.org>

Thanks for cleaning up after me!

> ---
>   drivers/char/hw_random/Kconfig | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig
> index dbf2271..ff00331 100644
> --- a/drivers/char/hw_random/Kconfig
> +++ b/drivers/char/hw_random/Kconfig
> @@ -372,6 +372,7 @@ config HW_RANDOM_XGENE
>   config HW_RANDOM_STM32
>   	tristate "STMicroelectronics STM32 random number generator"
>   	depends on HW_RANDOM && (ARCH_STM32 || COMPILE_TEST)
> +	depends on HAS_IOMEM
>   	help
>   	  This driver provides kernel-side support for the Random Number
>   	  Generator hardware found on STM32 microcontrollers.
>

  reply	other threads:[~2016-01-26  9:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1453760661-1444-1-git-send-email-richard@nod.at>
2016-01-25 22:24 ` [PATCH 05/22] hw_random: Fix dependencies for !HAS_IOMEM archs Richard Weinberger
2016-01-26  9:58   ` Daniel Thompson [this message]
2016-01-26 14:49   ` 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=56A7435B.5000405@linaro.org \
    --to=daniel.thompson@linaro.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kieranbingham@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=pankaj.dev@st.com \
    --cc=richard@nod.at \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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).