DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] devtools: add git log checks for DCB, TOS and TTL
Date: Tue, 29 Jan 2019 13:55:33 +0000	[thread overview]
Message-ID: <20190129135533.31723-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20190129132703.28954-1-ferruh.yigit@intel.com>

Add case check to DCB, TOS and TTL abbreviations.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
v2:
* fix typo, s/DBC/DCB/
---
 devtools/check-git-log.sh | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/devtools/check-git-log.sh b/devtools/check-git-log.sh
index d1c12049e..a905afc32 100755
--- a/devtools/check-git-log.sh
+++ b/devtools/check-git-log.sh
@@ -95,6 +95,7 @@ bad=$(echo "$headlines" | grep -E --color=always \
 	-e ':.*\<(Armv7|ARMv7|ArmV7|armV7|ARMV7)\>' \
 	-e ':.*\<(Armv8|ARMv8|ArmV8|armV8|ARMV8)\>' \
 	-e ':.*\<crc\>' \
+	-e ':.*\<dcb\>' \
 	-e ':.*\<dma\>' \
 	-e ':.*\<eeprom\>' \
 	-e ':.*\<freebsd\>' \
@@ -113,7 +114,9 @@ bad=$(echo "$headlines" | grep -E --color=always \
 	-e ':.*\<pmd\>' \
 	-e ':.*\<rss\>' \
 	-e ':.*\<sctp\>' \
+	-e ':.*\<tos\>' \
 	-e ':.*\<tso\>' \
+	-e ':.*\<ttl\>' \
 	-e ':.*\<udp\>' \
 	-e ':.*\<[Vv]lan\>' \
 	-e ':.*\<vdpa\>' \
-- 
2.17.2

  parent reply	other threads:[~2019-01-29 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 13:27 [dpdk-dev] [PATCH] devtools: add git log checks for DBC, " Ferruh Yigit
2019-01-29 13:49 ` Thomas Monjalon
2019-01-29 13:56   ` Ferruh Yigit
2019-01-29 13:55 ` Ferruh Yigit [this message]
2019-02-24 23:06   ` [dpdk-dev] [PATCH v2] devtools: add git log checks for DCB, " 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=20190129135533.31723-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).