From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 89CE0C433F5 for ; Mon, 7 Feb 2022 15:20:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237642AbiBGPTY (ORCPT ); Mon, 7 Feb 2022 10:19:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347334AbiBGOxQ (ORCPT ); Mon, 7 Feb 2022 09:53:16 -0500 Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [IPv6:2a0a:51c0:0:12e:520::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B6255C0401C1 for ; Mon, 7 Feb 2022 06:53:15 -0800 (PST) Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92) (envelope-from ) id 1nH5OD-0007bD-RG; Mon, 07 Feb 2022 15:53:13 +0100 Date: Mon, 7 Feb 2022 15:53:13 +0100 From: Florian Westphal To: Pablo Neira Ayuso Cc: Florian Westphal , netfilter-devel@vger.kernel.org Subject: Re: [PATCH nft 1/3] json: add flow statement json export + parser Message-ID: <20220207145313.GD25000@breakpoint.cc> References: <20220207132816.21129-1-fw@strlen.de> <20220207132816.21129-2-fw@strlen.de> <20220207132915.GB25000@breakpoint.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org Pablo Neira Ayuso wrote: > On Mon, Feb 07, 2022 at 02:29:15PM +0100, Florian Westphal wrote: > > Florian Westphal wrote: > > > flow statement has no export, its shown as: > > > ".. }, "flow add @ft" ] } }" > > > > > > With this patch: > > > > > > ".. }, {"flow": {"op": "add", "flowtable": "@ft"}}]}}" > > > > This is based on the 'set' statement. If you prefer the @ to > > be removed let me know. > > Then, it is consistent with the existing syntax. So either we consider > deprecating the @ on the 'set' statement (while retaining backward > compatibility) or flowtable also includes it as in your patch. Ok, then lets keep it as-is; the @ might help humans to find a set/flowtable name more quickly this way.