linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varun Wadekar <vwadekar@nvidia.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH v8 0/2] crypto: driver for Tegra AES hardware
Date: Fri, 13 Jan 2012 11:07:42 +0530	[thread overview]
Message-ID: <4F0FC326.7080307@nvidia.com> (raw)
In-Reply-To: <20120113053557.GA13918@gondor.apana.org.au>

On Friday 13 January 2012 11:05 AM, Herbert Xu wrote:
> On Fri, Dec 16, 2011 at 11:25:53AM +0000, Varun Wadekar wrote:
>> The tegra crypto driver uses the tegra_chip_uid API for the RNG
>> calculation. If one wants to build tegra-aes as a module, then
>> tegra_chip_uid needs to be exported.
> Both patches applied.  Thanks!

Thanks Herbert.

      reply	other threads:[~2012-01-13  5:37 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
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 [this message]

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=4F0FC326.7080307@nvidia.com \
    --to=vwadekar@nvidia.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.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).