linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Varun Wadekar <vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Henning Heinold <heinold-cPcqOTmdTlv31zTM6d8ziw@public.gmane.org>,
	herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org,
	davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Subject: Re: [PATCH v8 1/2] arm: tegra: export tegra_chip_uid
Date: Thu, 12 Jan 2012 16:09:51 +0530	[thread overview]
Message-ID: <4F0EB877.2050407@nvidia.com> (raw)
In-Reply-To: <1324034755-3295-2-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>

Add Herbert and David

On Friday 16 December 2011 04:55 PM, Varun Wadekar wrote:
> From: Henning Heinold<heinold-cPcqOTmdTlv31zTM6d8ziw@public.gmane.org>
>
> The crypto driver will need this api to use
> it in the RNG calculations. In order to build
> the crypto driver as a module, tegra_chip_uid
> has to be exported.
>
> Acked-by: Olof Johansson<olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
> Signed-off-by: Henning Heinold<heinold-cPcqOTmdTlv31zTM6d8ziw@public.gmane.org>
> Signed-off-by: Varun Wadekar<vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
>   arch/arm/mach-tegra/fuse.c |    2 ++
>   1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-tegra/fuse.c b/arch/arm/mach-tegra/fuse.c
> index 1fa26d9..ea49bd9 100644
> --- a/arch/arm/mach-tegra/fuse.c
> +++ b/arch/arm/mach-tegra/fuse.c
> @@ -19,6 +19,7 @@
>
>   #include<linux/kernel.h>
>   #include<linux/io.h>
> +#include<linux/module.h>
>
>   #include<mach/iomap.h>
>
> @@ -58,6 +59,7 @@ unsigned long long tegra_chip_uid(void)
>   	hi = fuse_readl(FUSE_UID_HIGH);
>   	return (hi<<  32ull) | lo;
>   }
> +EXPORT_SYMBOL(tegra_chip_uid);
>
>   int tegra_sku_id(void)
>   {

  parent reply	other threads:[~2012-01-12 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 11:25 [PATCH v8 0/2] crypto: driver for Tegra AES hardware Varun Wadekar
2011-12-16 11:25 ` [PATCH v8 1/2] arm: tegra: export tegra_chip_uid Varun Wadekar
     [not found]   ` <1324034755-3295-2-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-12 10:39     ` Varun Wadekar [this message]
2011-12-16 11:25 ` [PATCH v8 2/2] crypto: driver for Tegra AES hardware Varun Wadekar
     [not found]   ` <1324034755-3295-3-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-09  5:27     ` Varun Wadekar
     [not found]       ` <4F0A7AA9.6020104-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-10  5:29         ` Mark Brown
2012-01-12 10:40     ` Varun Wadekar
2011-12-16 19:58 ` [PATCH v8 0/2] " Stephen Warren
     [not found] ` <1324034755-3295-1-git-send-email-vwadekar-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-01-13  5:35   ` Herbert Xu
2012-01-13  5:37     ` Varun Wadekar

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=4F0EB877.2050407@nvidia.com \
    --to=vwadekar-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=heinold-cPcqOTmdTlv31zTM6d8ziw@public.gmane.org \
    --cc=herbert-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org \
    --cc=linux-crypto-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).