From: Rusty Russell <rusty@rustcorp.com.au>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Neil Horman <nhorman@tuxdriver.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"H. Peter Anvin" <hpa@zytor.com>,
"David S.Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, "Marco d'Itri" <md@linux.it>
Subject: Re: [PATCH] crypto: Add soft module dependency to load HW accelerated crypto modules
Date: Mon, 17 Feb 2014 11:04:16 +1030 [thread overview]
Message-ID: <87ob26d1br.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1392412566.27116.77.camel@schen9-DESK>
Tim Chen <tim.c.chen@linux.intel.com> writes:
> On Fri, 2014-02-14 at 15:28 -0500, Neil Horman wrote:
>> On Fri, Feb 14, 2014 at 11:14:37AM -0800, Tim Chen wrote:
>> > We added the soft module dependency of various crypto algorithm's module alias
>> > to generic crypto algorithm's module. This loads hardware accelerated
>> > modules and uses them when available.
>> >
>> This is great, but have any of the module load utilties been modified to
>> recognize and handle soft dependencies in the modinfo section? Last I checked
>> they hadn't. Do you plan to add that functionality?
>>
>> Neil
>>
>
> Rusty,
>
> Do you know if the upstream modprobe has the fixes (or plan) to
> recognize soft dependencies? I was under the impression that it
> is the case.
Marco CC'd...
Cheers,
Rusty.
next prev parent reply other threads:[~2014-02-17 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 19:14 [PATCH] crypto: Add soft module dependency to load HW accelerated crypto modules Tim Chen
2014-02-14 20:28 ` Neil Horman
2014-02-14 21:16 ` Tim Chen
2014-02-17 0:34 ` Rusty Russell [this message]
2014-02-17 1:21 ` Marco d'Itri
2014-02-17 1:56 ` Lucas De Marchi
2014-02-15 1:23 ` Herbert Xu
2014-02-15 2:01 ` Tim Chen
2014-02-15 23:41 ` Herbert Xu
2014-02-17 12:08 ` Neil Horman
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=87ob26d1br.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=md@linux.it \
--cc=nhorman@tuxdriver.com \
--cc=tim.c.chen@linux.intel.com \
/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.