I use some scripts to make some basic checks before committing or submitting some patches. As they can be useful for every DPDK developers and especially for new committers / tree owners, they are added to the scripts directory.
The problem, when sharing such tools, is how to make them customizable while fitting for everyone. The proposed solution is to use a development configuration file. Thomas Monjalon (2): scripts: add checkpatch wrapper scripts: add build tests scripts/checkpatches.sh | 82 ++++++++++++++++++++++++ scripts/load-devel-config.sh | 14 +++++ scripts/test-build.sh | 145 +++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 241 insertions(+) create mode 100755 scripts/checkpatches.sh create mode 100755 scripts/load-devel-config.sh create mode 100755 scripts/test-build.sh -- 2.5.2
