From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH v2] devtools: add git log checks for acronyms
Date: Fri, 27 Apr 2018 14:42:32 +0100 [thread overview]
Message-ID: <20180427134232.94035-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20180427132307.117503-1-ferruh.yigit@intel.com>
checks added for vDPA, MSS, UDP, EEPROM
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
v2:
* Add more checks: eeprom
---
devtools/check-git-log.sh | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/devtools/check-git-log.sh b/devtools/check-git-log.sh
index c601f6ae9..c8c149685 100755
--- a/devtools/check-git-log.sh
+++ b/devtools/check-git-log.sh
@@ -123,12 +123,14 @@ bad=$(echo "$headlines" | grep -E --color=always \
-e ':.*\<armv8\>' \
-e ':.*\<crc\>' \
-e ':.*\<dma\>' \
+ -e ':.*\<eeprom\>' \
-e ':.*\<freebsd\>' \
-e ':.*\<iova\>' \
-e ':.*\<linux\>' \
-e ':.*\<lro\>' \
-e ':.*\<lsc\>' \
-e ':.*\<mac\>' \
+ -e ':.*\<mss\>' \
-e ':.*\<mtu\>' \
-e ':.*\<nic\>' \
-e ':.*\<nvm\>' \
@@ -138,7 +140,9 @@ bad=$(echo "$headlines" | grep -E --color=always \
-e ':.*\<rss\>' \
-e ':.*\<sctp\>' \
-e ':.*\<tso\>' \
+ -e ':.*\<udp\>' \
-e ':.*\<[Vv]lan\>' \
+ -e ':.*\<vdpa\>' \
-e ':.*\<vsi\>' \
| sed 's,^,\t,')
[ -z "$bad" ] || printf "Wrong headline lowercase:\n$bad\n"
--
2.14.3
next prev parent reply other threads:[~2018-04-27 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 13:23 [dpdk-dev] [PATCH] devtools: add git log checks for vDPA MSS and UDP Ferruh Yigit
2018-04-27 13:42 ` Ferruh Yigit [this message]
2018-05-22 21:07 ` [dpdk-dev] [PATCH v2] devtools: add git log checks for acronyms 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=20180427134232.94035-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).