> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Wednesday, April 19, 2017 11:06 AM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Cc: zbigniew.bo...@caviumnetworks.com;
> jerin.ja...@caviumnetworks.com; Doherty, Declan
> Subject: RE: [PATCH 2/2] drvers/crypto: do not create unique name
> internally
>
>
> > -----Original Message-----
> > From: De Lara Guarch, Pablo
> > Sent: Tuesday, April 18, 2017 3:34 PM
> > To: dev@dpdk.org
> > Cc: zbigniew.bo...@caviumnetworks.com;
> > jerin.ja...@caviumnetworks.com; Doherty, Declan
> > <declan.dohe...@intel.com>; Zhang, Roy Fan
> <roy.fan.zh...@intel.com>;
> > De Lara Guarch, Pablo <pablo.de.lara.gua...@intel.com>
> > Subject: [PATCH 2/2] drvers/crypto: do not create unique name internally
> >
> > Crypto devices of the same type could be initialized with the same name,
> > since internally this name was suffixed with an index.
> >
> > Since commit <dda987315ca2> ("vdev: make virtual bus use its device
> struct"),
> > this is not allowed anymore.
> >
> > Therefore, there is no need to create an unique name at device
> initialization.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.gua...@intel.com>
>
> Hi Pablo,
>
> Typo in the title :-), should be drivers/crypto instead of drvers/crypto.
> Apart
> from that, everything is fine by me.
>
> Regards,
> Fan
>
> Acked-by: Fan Zhang <roy.fan.zh...@intel.com>
Title fixed, thanks!
Applied to dpdk-next-crypto.
Pablo
