All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] librte_ether: use RTE_ETH_VALID_PORTID_OR_ERR_RET to check port_id
Date: Tue, 24 May 2016 15:31:58 +0200	[thread overview]
Message-ID: <1829201.yogvSk4m0d@xps13> (raw)
In-Reply-To: <1463598911-18176-1-git-send-email-mauricio.vasquezbernal@studenti.polito.it>

2016-05-18 21:15, Mauricio Vasquez B:
> The RTE_ETH_VALID_PORTID_OR_ERR_RET macro is used in some places
> to check if a port id is valid or not. This commit makes use of it in
> some new parts of the code.
> 
> Signed-off-by: Mauricio Vasquez B <mauricio.vasquezbernal@studenti.polito.it>
> ---
> v3:
>  - use it also in rte_eth_add_rx_callback and rte_eth_add_tx_callback 
> v2:
>  - add missed case
>  - change also cases in examples/ethtool/lib/rte_ethtool.c
>  examples/ethtool/lib/rte_ethtool.c | 15 ++++++-----
>  lib/librte_ether/rte_ethdev.c      | 51 +++++++++++++-------------------------
>  2 files changed, 24 insertions(+), 42 deletions(-)

I've fixed also 2 bond functions and removed some whitespace changes.
Applied, thanks

      reply	other threads:[~2016-05-24 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 15:23 [PATCH] librte_ether: use RTE_ETH_VALID_PORTID_OR_ERR_RET to check port_id Mauricio Vasquez B
2016-05-13 16:20 ` Thomas Monjalon
2016-05-17 20:02   ` Mauricio Vásquez
2016-05-18  8:15     ` Thomas Monjalon
2016-05-18 14:41       ` Mauricio Vásquez
2016-05-18 15:01         ` Thomas Monjalon
2016-05-18 15:25           ` Mauricio Vásquez
2016-05-18 15:43             ` Thomas Monjalon
2016-05-18 19:14               ` Mauricio Vásquez
2016-05-17 20:01 ` [PATCH v2] " Mauricio Vasquez B
2016-05-18 19:15   ` [PATCH v3] " Mauricio Vasquez B
2016-05-24 13:31     ` Thomas Monjalon [this message]

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=1829201.yogvSk4m0d@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=mauricio.vasquezbernal@studenti.polito.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.