From: Arnon Warshavsky <arnon@qwilt.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH] devtools: check wrong svg include in patches
Date: Wed, 31 Oct 2018 17:46:56 +0200 [thread overview]
Message-ID: <CAKy9EB1D=92HkQ_LK+ZoLtCsCKNG60MnN6VAquXSs2OP+NU0xg@mail.gmail.com> (raw)
In-Reply-To: <20181031110548.31184-1-thomas@monjalon.net>
Hi Thomas
Glad the function gets to be reused :)
Now that it has more than one consumer apparently the function
check_forbidden_additions() cannot be fed by stdin.
I got it working with 3 changes:
1. call the awk script with $tmpinput as a parameter instead of stdin. This
aligns with Neils changes from previous version
2. Escaped the spaces from the regex , as the awk script uses spaces to
tell multiple forbidden expressions apart (which now I see sucks ...),
and added an extra backslash
3. call the function with no parameters (not needed anymore)
awk -v FOLDERS="lib drivers" \
-v EXPRESSIONS="rte_panic\\\( rte_exit\\\(" \
-v RET_ON_FAIL=1 \
- -f $(dirname $(readlink -e $0))/check-forbidden-tokens.awk -
+ -f $(dirname $(readlink -e $0))/check-forbidden-tokens.awk
*$tmpinput*
+
+ awk -v FOLDERS='doc' \
+ -v EXPRESSIONS='*::[[:space:]]*[^[:space:]]*\\\.svg*' \
+ -v RET_ON_FAIL=1 \
+ -f $(dirname $(readlink -e $0))/check-forbidden-tokens.awk
*$tmpinput*
! $verbose || printf '\nChecking forbidden tokens additions:\n'
- report=$(check_forbidden_additions *<"$tmpinput"*)
+ report=$(check_forbidden_additions)
thanks
/Arnon
next prev parent reply other threads:[~2018-10-31 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 11:05 Thomas Monjalon
2018-10-31 15:46 ` Arnon Warshavsky [this message]
2018-10-31 15:51 ` Thomas Monjalon
2018-10-31 15:55 ` Arnon Warshavsky
2018-10-31 16:28 ` [dpdk-dev] [PATCH v2] devtools: check wrong svg include in guides Thomas Monjalon
2018-11-01 6:45 ` Arnon Warshavsky
2018-11-01 9:27 ` Thomas Monjalon
2018-11-01 9:29 ` Arnon Warshavsky
2018-11-01 13:59 ` Arnon Warshavsky
2018-11-01 14:10 ` Thomas Monjalon
2018-11-01 21:25 ` 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='CAKy9EB1D=92HkQ_LK+ZoLtCsCKNG60MnN6VAquXSs2OP+NU0xg@mail.gmail.com' \
--to=arnon@qwilt.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--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).