From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: [dpdk-dev] [PATCH v2] scripts: add more git log checks
Date: Fri, 23 Sep 2016 13:47:27 +0100 [thread overview]
Message-ID: <20160923124727.30356-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20160920085303.24631-1-ferruh.yigit@intel.com>
Alphabetically sorted items to check and
added git log capitalization checks for LRO, NIC and PMD
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
scripts/check-git-log.sh | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/scripts/check-git-log.sh b/scripts/check-git-log.sh
index 1e05cf2..5f8a9fc 100755
--- a/scripts/check-git-log.sh
+++ b/scripts/check-git-log.sh
@@ -112,20 +112,23 @@ bad=$(echo "$headlines" | grep -E --color=always \
-e '\<[hsf]w\>' \
-e '\<l[234]\>' \
-e ':.*\<api\>' \
+ -e ':.*\<arm\>' \
+ -e ':.*\<armv7\>' \
+ -e ':.*\<armv8\>' \
-e ':.*\<dma\>' \
- -e ':.*\<pci\>' \
- -e ':.*\<mtu\>' \
+ -e ':.*\<freebsd\>' \
+ -e ':.*\<linux\>' \
+ -e ':.*\<lro\>' \
-e ':.*\<mac\>' \
+ -e ':.*\<mtu\>' \
+ -e ':.*\<nic\>' \
-e ':.*\<numa\>' \
- -e ':.*\<vlan\>' \
+ -e ':.*\<pci\>' \
+ -e ':.*\<pmd\>' \
-e ':.*\<rss\>' \
- -e ':.*\<freebsd\>' \
- -e ':.*\<linux\>' \
- -e ':.*\<tilegx\>' \
-e ':.*\<tile-gx\>' \
- -e ':.*\<arm\>' \
- -e ':.*\<armv7\>' \
- -e ':.*\<armv8\>' \
+ -e ':.*\<tilegx\>' \
+ -e ':.*\<vlan\>' \
| sed 's,^,\t,')
[ -z "$bad" ] || printf "Wrong headline lowercase:\n$bad\n"
--
2.7.4
next prev parent reply other threads:[~2016-09-23 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 8:53 [dpdk-dev] [PATCH] scripts: add git log check for NIC and LRO Ferruh Yigit
2016-09-23 12:47 ` Ferruh Yigit [this message]
2016-09-26 3:26 ` [dpdk-dev] [PATCH v2] scripts: add more git log checks Yuanhan Liu
2016-10-26 21:34 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160923124727.30356-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).