From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@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 10:58:41 -0800 [thread overview]
Message-ID: <20250212105841.03ccd91c@kernel.org> (raw)
In-Reply-To: <20250212182007.GG1615191@kernel.org>
On Wed, 12 Feb 2025 18:20:07 +0000 Simon Horman wrote:
> > > 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?
I'm not gonna say no :)
The problem is a bit broader than just this exact instance.
In general we don't clean up build artifacts to take advantage
of incremental builds. So when files move or get renamed the old
artifacts are left in place occasionally causing issues.
I wonder what the best fix is. Feels like wiping the tree clean
periodically (once a day or two?) could be best? Something like
creating a local file, once that file is more than 2 days old
wipe the tree pristine clean by all means possible, and then
create the file again?
next prev parent reply other threads:[~2025-02-12 18:58 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
2025-02-12 18:58 ` Jakub Kicinski [this message]
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=20250212105841.03ccd91c@kernel.org \
--to=kuba@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=fw@strlen.de \
--cc=horms@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 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).