From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
donald.hunter@gmail.com
Subject: Re: [PATCH v2 net-next] netlink: specs: add conntrack dump and stats dump support
Date: Wed, 12 Feb 2025 18:20:07 +0000 [thread overview]
Message-ID: <20250212182007.GG1615191@kernel.org> (raw)
In-Reply-To: <20250210125438.48560003@kernel.org>
On Mon, Feb 10, 2025 at 12:54:38PM -0800, Jakub Kicinski wrote:
> On Mon, 10 Feb 2025 21:27:03 +0100 Florian Westphal wrote:
> > Jakub Kicinski <kuba@kernel.org> wrote:
> > > On Mon, 10 Feb 2025 16:21:52 +0100 Florian Westphal wrote:
> > > > This adds support to dump the connection tracking table
> > > > ("conntrack -L") and the conntrack statistics, ("conntrack -S").
> > >
> > > Hi Florian!
> > >
> > > Some unhappiness in the HTML doc generation coming from this spec:
> > >
> > > /home/doc-build/testing/Documentation/networking/netlink_spec/ctnetlink.rst:68: WARNING: duplicate label conntrack-definition-nfgenmsg, other instance in /home/doc-build/testing/Documentation/networking/netlink_spec/conntrack.rst
> >
> > Looks like the tree has both v1 and v2 appliedto it.
> >
> > v1 added 'ctnetlink.yaml', I renamed it to 'conntrack.yaml' in v2 as
> > thats what Donald requested.
>
> I see. We need to clean the HTML output more thoroughly in the CI 🤔️
> I brought the patch back, let's see what happens on next run.
It seems happy now.
Should I work on a fix for NIPA?
next prev parent reply other threads:[~2025-02-12 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 15:21 [PATCH v2 net-next] netlink: specs: add conntrack dump and stats dump support Florian Westphal
2025-02-10 18:39 ` Jakub Kicinski
2025-02-10 20:27 ` Florian Westphal
2025-02-10 20:54 ` Jakub Kicinski
2025-02-12 18:20 ` Simon Horman [this message]
2025-02-12 18:58 ` Jakub Kicinski
2025-02-11 11:11 ` Donald Hunter
2025-02-13 4:10 ` 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=20250212182007.GG1615191@kernel.org \
--to=horms@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
/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.