From: Andrew Rybchenko <arybchenko@solarflare.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Liang Ma <liang.j.ma@intel.com>,
Peter Mccarthy <peter.mccarthy@intel.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Igor Russkikh <igor.russkikh@aquantia.com>,
Pavel Belous <pavel.belous@aquantia.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Marcin Wojtas <mw@semihalf.com>,
Michal Krawczyk <mk@semihalf.com>,
Guy Tzalik <gtzalik@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Xiao Wang <xiao.w.wang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Qiming Yang <qiming.yang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Rasesh Mody <rmody@marvell.com>,
Shahed Shaikh <shshaikh@marvell.com>,
"Yong Wang" <yongwang@vmware.com>,
Radu Nicolau <radu.nicolau@intel.com>,
"Akhil Goyal" <akhil.goyal@nxp.com>
Subject: [dpdk-dev] rte_errno set to negative value to be fixed
Date: Mon, 21 Jan 2019 19:26:54 +0300 [thread overview]
Message-ID: <dd3f069a-337b-310c-b183-3c62f47d3975@solarflare.com> (raw)
Hi all,
there are a number of cases where rte_errno is obviously set to negative
value. I think it should be fixed.
Regards,
Andrew.
$ git grep 'rte_errno = -E'
drivers/event/opdl/opdl_evdev.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev.c: rte_errno = -EDQUOT;
drivers/event/opdl/opdl_evdev.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -ENOSPC;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -ENOSPC;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -ENOSPC;
drivers/event/opdl/opdl_evdev_init.c: rte_errno = -EINVAL;
drivers/event/opdl/opdl_ring.c: rte_errno = -EINVAL;
drivers/event/sw/sw_evdev.c: rte_errno = -EDQUOT;
drivers/event/sw/sw_evdev.c: rte_errno = -EDQUOT;
drivers/event/sw/sw_evdev.c: rte_errno = -EDQUOT;
drivers/event/sw/sw_evdev.c: rte_errno = -EDQUOT;
drivers/net/atlantic/atl_rxtx.c: rte_errno = -EINVAL;
drivers/net/atlantic/atl_rxtx.c: rte_errno =
-ENOTSUP;
drivers/net/avf/avf_rxtx.c: rte_errno = -EINVAL;
drivers/net/avf/avf_rxtx.c: rte_errno = -EINVAL;
drivers/net/avf/avf_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/e1000/em_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/e1000/igb_rxtx.c: rte_errno = -EINVAL;
drivers/net/e1000/igb_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/ena/ena_ethdev.c: rte_errno = -ENOTSUP;
drivers/net/fm10k/fm10k_rxtx.c: rte_errno = -EINVAL;
drivers/net/fm10k/fm10k_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/i40e/i40e_rxtx.c: rte_errno = -EINVAL;
drivers/net/i40e/i40e_rxtx.c: rte_errno = -EINVAL;
drivers/net/i40e/i40e_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/i40e/i40e_rxtx.c: rte_errno = -EINVAL;
drivers/net/ice/ice_rxtx.c: rte_errno = -EINVAL;
drivers/net/ixgbe/ixgbe_rxtx.c: rte_errno = -EINVAL;
drivers/net/ixgbe/ixgbe_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/qede/qede_rxtx.c: rte_errno = -EINVAL;
drivers/net/qede/qede_rxtx.c: rte_errno = -EINVAL;
drivers/net/qede/qede_rxtx.c: rte_errno = -EINVAL;
drivers/net/qede/qede_rxtx.c: rte_errno = -ENOTSUP;
drivers/net/vmxnet3/vmxnet3_rxtx.c: rte_errno = -EINVAL;
drivers/net/vmxnet3/vmxnet3_rxtx.c: rte_errno =
-ENOTSUP;
examples/ipsec-secgw/sa.c: rte_errno = -ENOMEM;
lib/librte_eventdev/rte_event_eth_tx_adapter.h: rte_errno = -EINVAL;
lib/librte_eventdev/rte_event_eth_tx_adapter.h: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -ENOTSUP;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -ENOTSUP;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.c: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.h: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.h: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.h: rte_errno = -EINVAL;
lib/librte_eventdev/rte_eventdev.h: rte_errno = -EINVAL;
next reply other threads:[~2019-01-21 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 16:26 Andrew Rybchenko [this message]
2019-01-21 16:40 ` Burakov, Anatoly
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=dd3f069a-337b-310c-b183-3c62f47d3975@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=akhil.goyal@nxp.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=harry.van.haaren@intel.com \
--cc=igor.russkikh@aquantia.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=liang.j.ma@intel.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=pavel.belous@aquantia.com \
--cc=peter.mccarthy@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=radu.nicolau@intel.com \
--cc=rmody@marvell.com \
--cc=shshaikh@marvell.com \
--cc=wenzhuo.lu@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=yongwang@vmware.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).