From: Florian Westphal <fw@strlen.de>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, cmi@nvidia.com, nbd@nbd.name,
sven.auhagen@voleatech.de
Subject: Re: [PATCH nf-next 5/7] netfilter: conntrack: rework offload nf_conn timeout extension logic
Date: Thu, 26 Sep 2024 13:11:17 +0200 [thread overview]
Message-ID: <20240926111117.GB16642@breakpoint.cc> (raw)
In-Reply-To: <20240924194419.29936-6-fw@strlen.de>
Florian Westphal <fw@strlen.de> wrote:
> +/**
> + * nf_flow_table_tcp_timeout() - new timeout of offloaded tcp entry
> + * @ct: Flowtable offloaded tcp ct
> + *
> + * Return number of seconds when ct entry should expire.
This needs following kdoc fixup:
- * Return number of seconds when ct entry should expire.
+ * @return: number of seconds when ct entry should expire.
Rest of series doesn't add kdoc warnings.
next prev parent reply other threads:[~2024-09-26 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 19:44 [PATCH nf-next 0/7] netfilter: rework conntrack/flowtable interaction Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 1/7] netfilter: nft_flow_offload: clear tcp MAXACK flag before moving to slowpath Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 2/7] netfilter: nft_flow_offload: update tcp state flags under lock Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 3/7] netfilter: conntrack: remove skb argument from nf_ct_refresh Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 4/7] netfilter: flowtable: prefer plain nf_ct_refresh for setting initial timeout Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 5/7] netfilter: conntrack: rework offload nf_conn timeout extension logic Florian Westphal
2024-09-26 11:11 ` Florian Westphal [this message]
2024-09-24 19:44 ` [PATCH nf-next 6/7] netfilter: nft_flow_offload: never grow the timeout when moving packets back to slowpath Florian Westphal
2024-09-24 19:44 ` [PATCH nf-next 7/7] netfilter: nft_flow_offload: do not remove flowtable entry for fin packets Florian Westphal
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=20240926111117.GB16642@breakpoint.cc \
--to=fw@strlen.de \
--cc=cmi@nvidia.com \
--cc=nbd@nbd.name \
--cc=netfilter-devel@vger.kernel.org \
--cc=sven.auhagen@voleatech.de \
/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).