[dpdk-dev] [PATCH] aesni_mb: fix wrong return value

2016-02-24 Thread Thomas Monjalon
2016-02-18 15:39, Declan Doherty: > On 15/02/16 16:45, Pablo de Lara wrote: > > cryptodev_aesni_mb_init was returning the device id of > > the device just created, but rte_eal_vdev_init > > (the function that calls the first one), was expecting 0 or > > negative value. > > This made impossible to c

[dpdk-dev] [PATCH] aesni_mb: fix wrong return value

2016-02-18 Thread Declan Doherty
On 15/02/16 16:45, Pablo de Lara wrote: > cryptodev_aesni_mb_init was returning the device id of > the device just created, but rte_eal_vdev_init > (the function that calls the first one), was expecting 0 or > negative value. > This made impossible to create more than one aesni_mb device > from com

[dpdk-dev] [PATCH] aesni_mb: fix wrong return value

2016-02-15 Thread Pablo de Lara
cryptodev_aesni_mb_init was returning the device id of the device just created, but rte_eal_vdev_init (the function that calls the first one), was expecting 0 or negative value. This made impossible to create more than one aesni_mb device from command line. Fixes: 924e84f87306 ("aesni_mb: add driv