[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k0bubvhu.fsf@gmail.com>
Date: Tue, 12 Apr 2022 09:39:57 +0200
From: Joachim Wiberg <troglobit@...il.com>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: Roopa Prabhu <roopa@...dia.com>,
Nikolay Aleksandrov <razor@...ckwall.org>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
"bridge\@lists.linux-foundation.org"
<bridge@...ts.linux-foundation.org>,
"David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Tobias Waldekranz <tobias@...dekranz.com>
Subject: Re: [PATCH RFC net-next 05/13] selftests: forwarding: add TCPDUMP_EXTRA_FLAGS to lib.sh
On Mon, Apr 11, 2022 at 17:20, Vladimir Oltean <vladimir.oltean@....com> wrote:
> On Mon, Apr 11, 2022 at 03:38:29PM +0200, Joachim Wiberg wrote:
>> - $ns_cmd tcpdump -e -n -Q in -i $if_name \
>> + if [ -z $TCPDUMP_EXTRA_FLAGS ]; then
>> + extra_flags=""
>> + else
>> + extra_flags="$TCPDUMP_EXTRA_FLAGS"
>> + fi
>> +
>> + $ns_cmd tcpdump $extra_flags -e -n -Q in -i $if_name \
>
> Could you call directly "$ns_cmd tcpdump $TCPDUMP_EXTRA_FLAGS ..." here,
> without an intermediary "extra_flags" global variable which holds the
> same content?
>
> You could initialize it just like the way other variables are
> initialized, at the beginning of lib.sh:
>
> TCPDUMP_EXTRA_FLAGS=${TCPDUMP_EXTRA_FLAGS:=}
Ah, yes of course. Will fix in the next drop!
/J
Powered by blists - more mailing lists