From: Petr Machata <petrm@nvidia.com>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: Petr Machata <petrm@nvidia.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<horms@kernel.org>, <shuah@kernel.org>, <razor@blackwall.org>,
<netdev@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] selftests: net: lib: Fix jq parsing error
Date: Thu, 12 Feb 2026 10:51:15 +0100 [thread overview]
Message-ID: <87ms1e5jgm.fsf@nvidia.com> (raw)
In-Reply-To: <34e17499-e385-4017-801c-332c9c40d484@huawei.com>
Yue Haibing <yuehaibing@huawei.com> writes:
> On 2026/2/12 0:01, Petr Machata wrote:
>>
>> Yue Haibing <yuehaibing@huawei.com> writes:
>>
>>> ++ jq --arg flag UP 'any(.[].flags.[]; . == $flag)'
>>> jq: error: syntax error, unexpected '[', expecting FORMAT or QQSTRING_START
>>> (Unix shell quoting issues?) at <top-level>, line 1:
>>> any(.[].flags.[]; . == $flag)
>>> jq: 1 compile error
>>>
>>> Remove the extra dot (.) after flags array to fix this.
>>
>> Interesting, both work for me on 1.7.1. What jq version do you use?
>
> I run this on Ubuntu 23.04,
> jq - commandline JSON processor [version 1.6]
Hmm, I see, 1.6 doesn't seem to have accepted the syntax.
Thanks for the fix!
next prev parent reply other threads:[~2026-02-12 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 2:21 [PATCH net] selftests: net: lib: Fix jq parsing error Yue Haibing
2026-02-11 16:01 ` Petr Machata
2026-02-12 1:20 ` Yue Haibing
2026-02-12 9:51 ` Petr Machata [this message]
2026-02-13 2:50 ` patchwork-bot+netdevbpf
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=87ms1e5jgm.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.