From: Vivek Kutal <vivek.kutal@celunite.com>
To: Anderson Briglia <anderson.briglia@indt.org.br>
Cc: ext David Cohen <david.cohen@indt.org.br>,
linux-omap@vger.kernel.org,
linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 2/2] OMAP SHA1/MD5 module: Add suppor for SHA1/MD5 algorithm on OMAP.
Date: Wed, 12 Dec 2007 12:50:24 +0530 [thread overview]
Message-ID: <475F8BB8.9090404@celunite.com> (raw)
In-Reply-To: <475EA986.6080104@indt.org.br>
Isn't arch/arm/crypto a right place for this instead of drivers/crypto ?
--
Vivek
prev parent reply other threads:[~2007-12-12 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1196980234-14975-1-git-send-email-david.cohen@indt.org.br>
2007-12-11 15:10 ` [PATCH 1/2] OMAP Security HW accel: Adding base address and interruption on header files Anderson Briglia
[not found] ` <1196980234-14975-2-git-send-email-david.cohen@indt.org.br>
2007-12-11 15:15 ` [PATCH 2/2] OMAP SHA1/MD5 module: Add suppor for SHA1/MD5 algorithm on OMAP Anderson Briglia
2007-12-12 7:20 ` Vivek Kutal [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=475F8BB8.9090404@celunite.com \
--to=vivek.kutal@celunite.com \
--cc=anderson.briglia@indt.org.br \
--cc=david.cohen@indt.org.br \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@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