[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-13 Thread Thomas Monjalon
> > Bond device name was too long (grather than 32 signs) that cause mempool > > allocation to fail. > > > > Fixes: 92073ef961ee ("bond: unit tests") > > > > Signed-off-by: Michal Jastrzebski > > Acked-by: Bernard Iremonger Applied, thanks

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-08 Thread Thomas Monjalon
2016-06-08 11:50, Jastrzebski, MichalX K: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > 2016-05-27 18:38, Thomas Monjalon: > > > 2016-05-27 17:20, Michal Jastrzebski: > > > > Bond device name was too long (grather than 32 signs) that > > > > cause mempool allocation to fail. > >

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-08 Thread Jastrzebski, MichalX K
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, June 08, 2016 3:31 PM > To: Jastrzebski, MichalX K > Cc: Iremonger, Bernard ; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] app/test: fix bond device name too long

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-08 Thread Thomas Monjalon
2016-05-27 18:38, Thomas Monjalon: > 2016-05-27 17:20, Michal Jastrzebski: > > Bond device name was too long (grather than 32 signs) that > > cause mempool allocation to fail. > > Maybe that this kind of failure would be avoided if the test > was added to autotests (app/test/autotest_data.py). >

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-08 Thread Jastrzebski, MichalX K
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, June 08, 2016 12:40 PM > To: Jastrzebski, MichalX K ; Iremonger, > Bernard > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] app/test: fix bond device name too

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-01 Thread Xu, HuilongX
0623 (Red Hat 4.8.5-4) (GCC) Hugepage: 4096*2M > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michal Jastrzebski > Sent: Friday, May 27, 2016 11:21 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] app/test: fix bond device name too lo

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-06-01 Thread Xu, HuilongX
gcc version 4.8.5 20150623 (Red Hat 4.8.5-4) (GCC) Hugepage: 4096*2M > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michal Jastrzebski > Sent: Friday, May 27, 2016 11:21 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] app/test: fix bond d

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-05-27 Thread Thomas Monjalon
2016-05-27 17:20, Michal Jastrzebski: > Bond device name was too long (grather than 32 signs) that > cause mempool allocation to fail. Maybe that this kind of failure would be avoided if the test was added to autotests (app/test/autotest_data.py). Generally speaking, it would be a good idea to ma

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-05-27 Thread Michal Jastrzebski
Bond device name was too long (grather than 32 signs) that cause mempool allocation to fail. Fixes: 92073ef961ee ("bond: unit tests") Signed-off-by: Michal Jastrzebski --- app/test/test_link_bonding.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/test/test_link_bond

[dpdk-dev] [PATCH] app/test: fix bond device name too long

2016-05-27 Thread Iremonger, Bernard
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Michal Jastrzebski > Sent: Friday, May 27, 2016 4:21 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] app/test: fix bond device name too long > > Bond device name was too long (grathe