From: Martin Michlmayr <tbm@cyrius.com>
To: Sebastian Andrzej Siewior <arm-kernel@ml.breakpoint.cc>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-crypto@vger.kernel.org
Subject: Re: [WIP/RFC] crypto: add support for Orion5X crypto engine
Date: Wed, 18 Mar 2009 17:33:11 +0100 [thread overview]
Message-ID: <20090318163311.GN8453@deprecation.cyrius.com> (raw)
In-Reply-To: <49C11965.9000200@teltonika.lt>
* Paulius Zaleckas <paulius.zaleckas@teltonika.lt> [2009-03-18 17:55]:
> > +config CRYPTO_DEV_MARVELL_CRYPTO_ENGINE
>
> CRYPTO_DEV...CRYPTO_ENGINE
> Maybe CRYPTO_DEV_MARVELL would be enough?
... and since we're talking about naming issues, I think you should
replace "mav" with "mv" to be in line with other uses inside the
kernel (e.g. sata-mv).
Thanks for working on this driver!
--
Martin Michlmayr
http://www.cyrius.com/
prev parent reply other threads:[~2009-03-18 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 21:58 [WIP/RFC] crypto: add support for Orion5X crypto engine Sebastian Andrzej Siewior
2009-03-17 22:42 ` Evgeniy Polyakov
2009-03-18 21:57 ` Sebastian Andrzej Siewior
2009-03-18 15:55 ` Paulius Zaleckas
2009-03-18 16:33 ` Martin Michlmayr [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=20090318163311.GN8453@deprecation.cyrius.com \
--to=tbm@cyrius.com \
--cc=arm-kernel@ml.breakpoint.cc \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-crypto@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