From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: [dpdk-dev] [PATCH 1/2] scripts: fix false positive warning
Date: Tue, 10 May 2016 21:09:00 -0700 [thread overview]
Message-ID: <1462939741-12357-2-git-send-email-yuanhan.liu@linux.intel.com> (raw)
In-Reply-To: <1462939741-12357-1-git-send-email-yuanhan.liu@linux.intel.com>
It reports an false positive warning when the commit subject includes
the word "ctx", as it matches following regexp:
-e 'rx\|tx\|RX\|TX'
Fixes: edbeb7d962e9 ("scripts: check commit formatting")
Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
---
scripts/check-git-log.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/check-git-log.sh b/scripts/check-git-log.sh
index ce6c15e..b7ea1be 100755
--- a/scripts/check-git-log.sh
+++ b/scripts/check-git-log.sh
@@ -86,8 +86,8 @@ bad=$(echo "$headlines" | grep \
[ -z "$bad" ] || printf "Wrong headline uppercase:\n$bad\n"
# check headline uppercase (Rx/Tx, VF, L2, MAC, Linux, ARM...)
-bad=$(echo "$headlines" | grep \
- -e 'rx\|tx\|RX\|TX' \
+bad=$(echo "$headlines" | grep -E \
+ -e '\<(rx|tx|RX|TX)\>' \
-e '\<[pv]f\>' \
-e '\<l[234]\>' \
-e ':.*\<dma\>' \
--
1.9.0
next prev parent reply other threads:[~2016-05-11 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 4:08 [dpdk-dev] [PATCH 0/2] check-git-log fix and enhancement Yuanhan Liu
2016-05-11 4:09 ` Yuanhan Liu [this message]
2016-05-11 4:09 ` [dpdk-dev] [PATCH 2/2 RFC] scripts: high light bad patterns Yuanhan Liu
2016-05-24 14:48 ` [dpdk-dev] [PATCH 0/2] check-git-log fix and enhancement 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=1462939741-12357-2-git-send-email-yuanhan.liu@linux.intel.com \
--to=yuanhan.liu@linux.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).