From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: [PATCH v2 0/2] more basic tests Date: Mon, 23 Nov 2015 02:40:06 +0100 Message-ID: <1448242808-16101-1-git-send-email-thomas.monjalon@6wind.com> References: <1445615606-3885-1-git-send-email-thomas.monjalon@6wind.com> To: dev@dpdk.org Return-path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id 33158688E for ; Mon, 23 Nov 2015 02:41:29 +0100 (CET) Received: by wmvv187 with SMTP id v187so140425417wmv.1 for ; Sun, 22 Nov 2015 17:41:29 -0800 (PST) In-Reply-To: <1445615606-3885-1-git-send-email-thomas.monjalon@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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