From: Gopal Yadav <gopunop@gmail.com>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] Solves Bug 1462 - `nft -j list set` does not show counters
Date: Fri, 9 Oct 2020 11:15:48 +0530 [thread overview]
Message-ID: <CAAUOv8hXEA=2fM5UBN8xGkquO9EHMzCQ=kdEyFukDK7zPSeXow@mail.gmail.com> (raw)
In-Reply-To: <20201008170245.GC13016@orbyte.nwl.cc>
On Thu, Oct 8, 2020 at 10:32 PM Phil Sutter <phil@nwl.cc> wrote:
>
> On Wed, Oct 07, 2020 at 07:33:37PM +0530, Gopal Yadav wrote:
> > Solves Bug 1462 - `nft -j list set` does not show counters
> >
> > Signed-off-by: Gopal Yadav <gopunop@gmail.com>
>
> Added a comment about potential clashes (json_object_update_missing()
> hides those) and replaced the duplicate subject line by a commit
> message, then applied the result.
Any description of those potential clashes?
next prev parent reply other threads:[~2020-10-09 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 14:03 [PATCH v2] Solves Bug 1462 - `nft -j list set` does not show counters Gopal Yadav
2020-10-08 17:02 ` Phil Sutter
2020-10-09 5:45 ` Gopal Yadav [this message]
2020-10-09 8:31 ` Phil Sutter
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='CAAUOv8hXEA=2fM5UBN8xGkquO9EHMzCQ=kdEyFukDK7zPSeXow@mail.gmail.com' \
--to=gopunop@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).