From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] hwrng: msm: switch Kconfig to ARCH_QCOM depends
Date: Thu, 20 Feb 2014 13:42:17 -0500 [thread overview]
Message-ID: <53064C89.4060206@codeaurora.org> (raw)
In-Reply-To: <1392912542-5349-1-git-send-email-galak@codeaurora.org>
On 02/20/2014 11:09 AM, Kumar Gala wrote:
> We've split Qualcomm MSM support into legacy and multiplatform. The RNG
> driver is only relevant on the multiplatform supported SoCs so switch the
> Kconfig depends to ARCH_QCOM.
>
> CC: Herbert Xu <herbert@gondor.apana.org.au>
> CC: Stanimir Varbanov <svarbanov@mm-sol.com>
> Signed-off-by: Kumar Gala <galak@codeaurora.org>
> ---
>
> Herbert,
>
> If you can ack this I'll send it via linux-qcom/arm-soc tree's
>
> thanks
>
> v2:
> * Updated help text to remove MSM references, made more generic
>
> drivers/char/hw_random/Kconfig | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig
> index 2f2b084..f2b9f8c 100644
> --- a/drivers/char/hw_random/Kconfig
> +++ b/drivers/char/hw_random/Kconfig
> @@ -342,11 +342,11 @@ config HW_RANDOM_TPM
> If unsure, say Y.
>
> config HW_RANDOM_MSM
> - tristate "Qualcomm MSM Random Number Generator support"
> + tristate "Qualcomm ARM SoCs Random Number Generator support"
Can the Hexagon use the PRNG, at least theoretically? If so maybe it'd be
clearest to leave ARM off.
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-02-20 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 16:09 [PATCH v2] hwrng: msm: switch Kconfig to ARCH_QCOM depends Kumar Gala
2014-02-20 18:42 ` Christopher Covington [this message]
2014-02-20 21:54 ` Kumar Gala
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=53064C89.4060206@codeaurora.org \
--to=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).