From: Arnd Bergmann <arnd@arndb.de>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: sonic.zhang@analog.com, LKML <linux-kernel@vger.kernel.org>,
uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH] driver: char: bfin_crc: CRC hardware accelerator driver for BF60x family processors.
Date: Wed, 16 May 2012 15:11:26 +0000 [thread overview]
Message-ID: <201205161511.27232.arnd@arndb.de> (raw)
In-Reply-To: <20120516145333.GB1139@kroah.com>
On Wednesday 16 May 2012, Greg Kroah-Hartman wrote:
> > Do we have a userspace crypto API these days? The last I remember every
> > attempt to add one so far was abandoned before it got merged. There is
> > drivers/s390/crypto/zcrypt*, which has a nonportable API, and
> > then there is the in-kernel crypto layer in drivers/crypto that has
> > no user interface at all.
>
> What is CONFIG_CRYPTO_USER for then, with the matching,
> crypto/crypto_user.c file?
Ah, I completely missed that going in and looked in the wrong place
when trying to find it now (/drivers/crypto, not /crypto). I'm glad
that part is resolved.
> > I agree that having another private driver for bfin_crc is not a good
> > idea, but I also don't have a better one.
> >
> > About the driver itself, the submission seems incomplete (missing at
> > least the bfin_crc.h file) and the driver has a number of shortcomings
> > that we should discuss in case we decide to merge it.
>
> I suggest at least tieing into the in-kernel crypto api first, and then
> worrying about the userspace side of things, right?
Absolutely.
Arnd
next prev parent reply other threads:[~2012-05-16 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 8:26 sonic.zhang
2012-05-16 12:12 ` Greg Kroah-Hartman
2012-05-16 13:39 ` Arnd Bergmann
2012-05-16 14:53 ` Greg Kroah-Hartman
2012-05-16 15:11 ` Arnd Bergmann [this message]
2012-05-17 10:55 ` Zhang, Sonic
2012-05-17 13:40 ` Greg Kroah-Hartman
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=201205161511.27232.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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
Powered by JetHome