Go to file
Jerin Jacob 98a7ea332b fix typos using codespell utility
Fixing typos across dpdk source code using codespell utility.
Skipped the ethdev driver's base code fixes to keep the base
code intact.

Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
2017-06-14 23:54:13 +02:00
app fix typos using codespell utility 2017-06-14 23:54:13 +02:00
buildtools mk: optimize directory dependencies 2017-03-27 23:28:43 +02:00
config net/szedata2: add more supported firmwares 2017-06-12 15:21:22 +01:00
devtools fix typos using codespell utility 2017-06-14 23:54:13 +02:00
doc fix typos using codespell utility 2017-06-14 23:54:13 +02:00
drivers fix typos using codespell utility 2017-06-14 23:54:13 +02:00
examples fix typos using codespell utility 2017-06-14 23:54:13 +02:00
lib fix typos using codespell utility 2017-06-14 23:54:13 +02:00
mk fix typos using codespell utility 2017-06-14 23:54:13 +02:00
pkg version: 17.05.0 2017-05-11 03:11:34 +02:00
test fix typos using codespell utility 2017-06-14 23:54:13 +02:00
usertools usertools: add Cavium pkx as network device 2017-05-07 14:32:17 +02:00
.gitattributes improve git diff 2016-11-13 15:25:12 +01:00
.gitignore devtools: add tags and cscope index generation 2017-04-30 12:57:04 +02:00
GNUmakefile mk: do not build tests by default 2017-02-28 16:04:18 +01:00
LICENSE.GPL doc: GPL/LGPL licenses 2013-07-25 14:43:06 +02:00
LICENSE.LGPL doc: fix file format (dos to unix) 2013-09-06 11:43:07 +02:00
MAINTAINERS maintainers: update email address 2017-06-02 16:37:29 +02:00
Makefile remove trailing whitespaces 2014-06-11 00:29:34 +02:00
README doc: add readme file 2015-12-13 22:06:58 +01:00

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 license for the core libraries and
drivers. The kernel components are GPLv2 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