From: Paul Mundt <lethal@linux-sh.org>
To: Ben Nizette <bn@niasdigital.com>
Cc: Hans-J?rgen Koch <hjk@linutronix.de>, gregkh <gregkh@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] UIO: Implement a UIO interface for the SMX Cryptengine
Date: Thu, 13 Mar 2008 22:21:10 +0900 [thread overview]
Message-ID: <20080313132110.GA14422@linux-sh.org> (raw)
In-Reply-To: <1205407650.3735.19.camel@moss.renham>
On Thu, Mar 13, 2008 at 10:27:30PM +1100, Ben Nizette wrote:
> This patch implements a UIO interface for the SMX Cryptengine.
>
> The Cryptengine found on the Nias Digital SMX board is best suited
> for a UIO interface. It is not wired in to the cryptographic API
> as the engine handles it's own keys, algorithms, everything. All
> that we know about is that if there's room in the buffer, you can
> write data to it and when there's data ready, you read it out again.
>
> There isn't necessarily even any direct correlation between data
> going in and data coming out again, the engine may consume or
> generate data all on its own.
>
> This driver is for proprietary hardware but we're always told to
> submit the drivers anyway; here you are. :-)
>
> This is version 4 of this patch and addresses all issues raised by
> Hans-J??rgen Koch and Paul Mundt in their reviews. Slightly altered
> is Paul's suggestion to use DRV_NAME and DRV_VERSION as the UIO
> version and name. While at the moment they are the same, there
> is no reason for them to stay that way. Nevertheless we now at
> least provide a MODULE_VERSION macro to keep modinfo happy.
>
Looks good to me.
next prev parent reply other threads:[~2008-03-13 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 11:27 [PATCH v4] UIO: Implement a UIO interface for the SMX Cryptengine Ben Nizette
2008-03-13 13:21 ` Paul Mundt [this message]
2008-03-13 14:31 ` Hans-Jürgen Koch
2008-03-13 20:54 ` patch uio-implement-a-uio-interface-for-the-smx-cryptengine.patch added to gregkh-2.6 tree gregkh
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=20080313132110.GA14422@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=bn@niasdigital.com \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.