patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Xiaolong Ye <xiaolong.ye@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] ethdev: fix typos for ENOTSUP
Date: Wed, 4 Sep 2019 07:59:25 -0700	[thread overview]
Message-ID: <20190904075925.5cdeca26@hermes.lan> (raw)
In-Reply-To: <20190904140531.65581-1-xiaolong.ye@intel.com>

On Wed,  4 Sep 2019 22:05:31 +0800
Xiaolong Ye <xiaolong.ye@intel.com> wrote:

> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
> ---
>  lib/librte_ethdev/rte_ethdev.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
> index dc6596bc9..51e2caf79 100644
> --- a/lib/librte_ethdev/rte_ethdev.h
> +++ b/lib/librte_ethdev/rte_ethdev.h
> @@ -2477,7 +2477,7 @@ int rte_eth_dev_set_mtu(uint16_t port_id, uint16_t mtu);
>   *   Otherwise, disable VLAN filtering of VLAN packets tagged with *vlan_id*.
>   * @return
>   *   - (0) if successful.
> - *   - (-ENOSUP) if hardware-assisted VLAN filtering not configured.
> + *   - (-ENOTSUP) if hardware-assisted VLAN filtering not configured.
>   *   - (-ENODEV) if *port_id* invalid.
>   *   - (-EIO) if device is removed.
>   *   - (-ENOSYS) if VLAN filtering on *port_id* disabled.
> @@ -2500,7 +2500,7 @@ int rte_eth_dev_vlan_filter(uint16_t port_id, uint16_t vlan_id, int on);
>   *   If 0, Disable VLAN Stripping of the receive queue of the Ethernet port.
>   * @return
>   *   - (0) if successful.
> - *   - (-ENOSUP) if hardware-assisted VLAN stripping not configured.
> + *   - (-ENOTSUP) if hardware-assisted VLAN stripping not configured.
>   *   - (-ENODEV) if *port_id* invalid.
>   *   - (-EINVAL) if *rx_queue_id* invalid.
>   */
> @@ -2520,7 +2520,7 @@ int rte_eth_dev_set_vlan_strip_on_queue(uint16_t port_id, uint16_t rx_queue_id,
>   *   The Tag Protocol ID
>   * @return
>   *   - (0) if successful.
> - *   - (-ENOSUP) if hardware-assisted VLAN TPID setup is not supported.
> + *   - (-ENOTSUP) if hardware-assisted VLAN TPID setup is not supported.
>   *   - (-ENODEV) if *port_id* invalid.
>   *   - (-EIO) if device is removed.
>   */
> @@ -2546,7 +2546,7 @@ int rte_eth_dev_set_vlan_ether_type(uint16_t port_id,
>   *       ETH_QINQ_STRIP_OFFLOAD
>   * @return
>   *   - (0) if successful.
> - *   - (-ENOSUP) if hardware-assisted VLAN filtering not configured.
> + *   - (-ENOTSUP) if hardware-assisted VLAN filtering not configured.
>   *   - (-ENODEV) if *port_id* invalid.
>   *   - (-EIO) if device is removed.
>   */

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  reply	other threads:[~2019-09-04 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 14:05 [dpdk-stable] " Xiaolong Ye
2019-09-04 14:59 ` Stephen Hemminger [this message]
2019-09-05 17:11   ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit

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=20190904075925.5cdeca26@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiaolong.ye@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).