From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig
Date: Fri, 18 Mar 2016 14:46:39 +0000 [thread overview]
Message-ID: <20160318144639.GH19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <87oaab980n.fsf@free-electrons.com>
On Fri, Mar 18, 2016 at 03:26:48PM +0100, Gregory CLEMENT wrote:
> For Dove I don't know if there are users for this module, but for Orion
> and Kirkwood as they are used in NAS product, I am pretty sure that
> people use it. I would like to have some feedback about users which have
> switched to the new driver. I think Jason did it on kirkwood.
I've tested it (and sent patches to fix issues found) with Dove. As it
works on Dove, there's no reason not to have it enabled on Dove.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-03-18 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 8:12 [PATCH] ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig Romain Perier
2016-03-18 13:14 ` Andrew Lunn
2016-03-18 13:51 ` Thomas Petazzoni
2016-03-18 14:26 ` Gregory CLEMENT
2016-03-18 14:46 ` Russell King - ARM Linux [this message]
2016-03-18 15:35 ` Thomas Petazzoni
2016-03-18 15:45 ` Russell King - ARM Linux
2016-03-18 15:52 ` Thomas Petazzoni
2016-03-18 16:22 ` Russell King - ARM Linux
2016-03-19 17:48 ` Jason Cooper
2016-03-18 14:30 ` Andrew Lunn
2016-03-18 15:05 ` Romain Perier
2016-03-18 15:18 ` Russell King - ARM Linux
2016-03-18 15:37 ` Thomas Petazzoni
2016-03-18 14:21 ` Gregory CLEMENT
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=20160318144639.GH19428@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).