0ff708ed6f
There is no point in having non-static (and non-extern) inline functions. Also this breaks the build for the ICC [1] because of the 'internal' symbol check. When function is 'inline' ICC is ignoring 'section' attribute and not putting function to 'internal' section which breaks 'check-symbols.sh' script with below error. [1] qbman_swp_dqrr_next is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_dqrr_next qbman_swp_enqueue_multiple is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_enqueue_multiple qbman_swp_enqueue_multiple_desc is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_enqueue_multiple_desc qbman_swp_enqueue_multiple_fd is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_enqueue_multiple_fd qbman_swp_pull is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_pull qbman_swp_release is not flagged as internal but is listed in version map Please add __rte_internal to the definition of qbman_swp_release Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> |
||
|---|---|---|
| .ci | ||
| app | ||
| buildtools | ||
| config | ||
| devtools | ||
| doc | ||
| drivers | ||
| examples | ||
| kernel | ||
| lib | ||
| license | ||
| mk | ||
| usertools | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .travis.yml | ||
| ABI_VERSION | ||
| GNUmakefile | ||
| MAINTAINERS | ||
| Makefile | ||
| meson_options.txt | ||
| meson.build | ||
| README | ||
| VERSION | ||
DPDK is a set of libraries and drivers for fast packet processing. It supports many processor architectures and both FreeBSD and Linux. The DPDK uses the Open Source BSD-3-Clause license for the core libraries and drivers. The kernel components are GPL-2.0 licensed. Please check the doc directory for release notes, API documentation, and sample application information. For questions and usage discussions, subscribe to: users@dpdk.org Report bugs and issues to the development mailing list: dev@dpdk.org