[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

> > This patch series include a fix and an improvement to rte_ethdev lib. > > > > Jia Yu (2): > > rte_ethdev: update link status (speed, duplex, link_up) after > > rte_eth_dev_start > > rte_ethdev: add return status for rte_eth_stats_get > > Acked-by: Helin Zhang Applied, thanks

[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jia Yu > Sent: Saturday, November 8, 2014 1:32 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement > > This patch series include a fix and an improvem

[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

2014-11-11 23:48, Jia Yu: > The two patches are minor fixes. No new API is introduced. You are changing the API of rte_eth_stats_get(). It's a tricky corner case because it's a light change which should have no impact. Anyone against changing the void return into int? Impact in mind? I can integra

[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

Thanks, Thomas. The two patches are minor fixes. No new API is introduced. I will revise the description. Thanks, Jia On 11/10/14, 1:40 AM, "Thomas Monjalon" wrote: >Hi Jia, > >2014-11-07 09:31, Jia Yu: >> This patch series include a fix and an improvement to rte_ethdev lib. > >New enhancement

[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

Hi Jia, 2014-11-07 09:31, Jia Yu: > This patch series include a fix and an improvement to rte_ethdev lib. New enhancements won't be integrated in release 1.8. But fixes are welcome. The problem is that it's not easy to track partially applies patchset. So it would be simpler if you send your fix

[dpdk-dev] [PATCH 0/2] rte_ethdev fix/improvement

This patch series include a fix and an improvement to rte_ethdev lib. Jia Yu (2): rte_ethdev: update link status (speed, duplex, link_up) after rte_eth_dev_start rte_ethdev: add return status for rte_eth_stats_get lib/librte_ether/rte_ethdev.c | 11 --- lib/librte_ether/rte_ethde