nfp_fl_ct_clean_flow_entry(9)

🌸 nfp_fl_ct_clean_flow_entry — Kernel API Manual, bestie edition 🌸

Okay so this page is from the Kernel API Manual, and it’s all about nfp_fl_ct_clean_flow_entry(9). Tiny cleanup-helper energy, very “handle this so I don’t have to” 💅. Let’s get into it, no cap.

---

✨ NAME ✨

nfp_fl_ct_clean_flow_entry — free a nfp_fl_ct_flow_entry

Like, that’s the whole plot: it’s the function for freeing a nfp_fl_ct_flow_entry. Iconic, concise, we love that for us. 🎀

---

🌈 SYNOPSIS 🌈

void nfp_fl_ct_clean_flow_entry (struct nfp_fl_ct_flow_entry *entry );

There it is, character for character. It returns void, and it takes one argument named entry. 🫶

---

🎀 ARGUMENTS 🎀

• entry — the flow entry to cleanup. That’s the thing you’re handing over for cleanup, bestie. 🧚

---

💖 SEE ALSO 💖

First up, the kernel file:

• ./drivers/net/ethernet/netronome/nfp/flower/conntrack.h

And then the whole friend group:

• struct nfp_fl_ct_zone_entry(9)
• struct nfp_fl_ct_flow_entry(9)
• struct nfp_fl_ct_tc_merge(9)
• struct nfp_fl_nft_tc_merge(9)
• struct nfp_fl_ct_map_entry(9)
• nfp_fl_ct_handle_pre_ct(9)
• nfp_fl_ct_handle_post_ct(9)
• nfp_fl_create_new_pre_ct(9)
• nfp_fl_ct_del_flow(9)
• nfp_fl_ct_handle_nft_flow(9)
• nfp_fl_ct_stats(9)

All of those are linked in spirit, and we are not skipping a single one. Periodt. 💜

---

And that’s the cute little sign-off: the source/version line says ./drivers/net/ethernet/netrono..., the date is October 2026, and the footer also has nfp_fl_ct_clean_flow_entry(9) in it. Slay. 🌟💖