The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Youquan,Song" <youquan.song@linux.intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Youquan,Song" <youquan.song@linux.intel.com>,
	linux-kernel@vger.kernel.org, ying.huang@intel.com,
	kent.liu@intel.com, youquan.song@intel.com
Subject: Re: [PATCH]crypto: Fix algorithm and driver duplicate registered
Date: Thu, 19 Nov 2009 06:02:22 -0500	[thread overview]
Message-ID: <20091119110222.GA19379@youquan-linux.bj.intel.com> (raw)
In-Reply-To: <20091119001827.GC2315@gondor.apana.org.au>

On Thu, Nov 19, 2009 at 08:18:27AM +0800, Herbert Xu wrote:
> On Wed, Nov 18, 2009 at 07:32:02PM -0500, Youquan,Song wrote:
> > Current kernel, All the algorithms with same algorithm name and driver name
> > are registered. 
> > But the proper behaviour should be only one algorithm be registered when 
> > algorithm and driver name duplicate.
> > 
> > Signed-off-by: Youquan, Song <youquan.song@intel.com>
> 
> This is intentional, in order to allow older implementations to be
> replaced on the fly.
> 
> Is this causing any issues for you?

I have watched crypto_alg_list includes several duplicate algorithms
with same algorithm name and driver name. 
Since they are the same algorithms, one is only needed. otherwise,it
will make some confusion.

Thanks.

  reply	other threads:[~2009-11-19  3:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19  0:32 [PATCH]crypto: Fix algorithm and driver duplicate registered Youquan,Song
2009-11-19  0:18 ` Herbert Xu
2009-11-19 11:02   ` Youquan,Song [this message]
2009-11-19 11:47     ` Herbert Xu
2009-11-23 17:21       ` Youquan,Song
2009-11-23 10:52         ` Herbert Xu
2009-11-23 17:47       ` Youquan,Song
2009-11-23 11:31         ` Herbert Xu
2009-11-25 10:35           ` Youquan,Song
2009-11-25  3:12             ` Herbert Xu

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=20091119110222.GA19379@youquan-linux.bj.intel.com \
    --to=youquan.song@linux.intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kent.liu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    --cc=youquan.song@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox