All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, Jingjing Wu <jingjing.wu@intel.com>
Subject: Re: [PATCH v2 2/3] ethdev: add device iterator
Date: Wed, 05 Apr 2017 22:42:23 +0200	[thread overview]
Message-ID: <1515202.sbJ8BQFpaS@xps13> (raw)
In-Reply-To: <3ae96511a71fa9f79be09eb518e7837c9a637599.1490961533.git.gaetan.rivet@6wind.com>

2017-03-31 14:04, Gaetan Rivet:
>  /**
> + * Iterates over valid ethdev ports.
> + *
> + * @param: port_id

warning: expected whitespace after : command

Will fix it when applying

> + *   The id of the next possible valid port.
> + * @return
> + *   Next valid port id, RTE_MAX_ETHPORTS if there is none.
> + */
> +uint8_t rte_eth_find_next(uint8_t port_id);
> 

  reply	other threads:[~2017-04-05 20:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 15:40 [PATCH 0/4] clarify eth_dev state management Gaetan Rivet
2017-03-03 15:40 ` [PATCH 1/4] ethdev: expose device states Gaetan Rivet
2017-03-03 15:40 ` [PATCH 2/4] ethdev: add device iterator Gaetan Rivet
2017-03-03 15:40 ` [PATCH 3/4] ethdev: count devices consistently Gaetan Rivet
2017-03-30 19:26   ` Thomas Monjalon
2017-03-31  9:13     ` Gaëtan Rivet
2017-03-03 15:40 ` [PATCH 4/4] app/testpmd: use ethdev iterator to list devices Gaetan Rivet
2017-03-31 12:04 ` [PATCH v2 0/3] clarify eth_dev state management Gaetan Rivet
2017-03-31 12:04   ` [PATCH v2 1/3] ethdev: expose device states Gaetan Rivet
2017-03-31 12:04   ` [PATCH v2 2/3] ethdev: add device iterator Gaetan Rivet
2017-04-05 20:42     ` Thomas Monjalon [this message]
2017-03-31 12:04   ` [PATCH v2 3/3] app/testpmd: use ethdev iterator to list devices Gaetan Rivet
2017-04-05 20:46   ` [PATCH v2 0/3] clarify eth_dev state management Thomas Monjalon

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=1515202.sbJ8BQFpaS@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.com \
    --cc=jingjing.wu@intel.com \
    /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.