From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: [PATCH 0/2] more basic tests Date: Fri, 23 Oct 2015 17:53:24 +0200 Message-ID: <1445615606-3885-1-git-send-email-thomas.monjalon@6wind.com> To: dev@dpdk.org Return-path: Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by dpdk.org (Postfix) with ESMTP id BD6DD5A17 for ; Fri, 23 Oct 2015 17:54:38 +0200 (CEST) Received: by wijp11 with SMTP id p11so83689085wij.0 for ; Fri, 23 Oct 2015 08:54:37 -0700 (PDT) Received: from localhost.localdomain (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id cq8sm2187837wib.12.2015.10.23.08.54.36 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Oct 2015 08:54:36 -0700 (PDT) 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. I think they can be useful for every DPDK developers and especially for new committers / tree owners. The problem when sharing such tool is how to make it 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 | 30 ++++++++++++ scripts/load-devel-config.sh | 14 ++++++ scripts/test-build.sh | 112 +++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 156 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