ntmp_ipft_add_entry(9)

💖 ntmp_ipft_add_entry(9) — like, the Kernel API Manual, but make it make sense 💖

okay so bestie, welcome to the ntmp_ipft_add_entry(9) era 🎀 this is a Kernel API Manual page and it's literally about dropping a new entry into the ingress port filter table. yes, that table. slay.

---

✨ NAME ✨

ntmp_ipft_add_entry — add an entry into the ingress port filter table 🦋

---

🌸 SYNOPSIS 🌸

int ntmp_ipft_add_entry (struct ntmp_user *user , struct ipft_entry_data
*entry );

---

💅 ARGUMENTS 💅

• user — the target ntmp_user struct. like, the user struct we're aiming at, yk? 👑
• entry — the entry data. okay so this one's doing the heavy lifting: entry->cfge (configuration element data) and entry->keye (key element data) are used as input. no cap. BUT — and this is the plot twist 🫶 — the entry ID is assigned by the hardware, so entry->entry_id is a returned value for the driver to use. once the driver has that entry_id, it can update/delete/query the entry based on it. main character energy fr fr.

---

🔥 RETURN 🔥

0 on success, otherwise a negative error code 😭 that's it, that's the whole vibe check.

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/ethernet/freescale/enetc/ntmp.c 🧚

• ntmp_ipft_delete_entry(9)
• ntmp_fdbt_add_entry(9)
• ntmp_fdbt_update_entry(9)
• ntmp_fdbt_delete_entry(9)
• ntmp_fdbt_search_port_entry(9)
• ntmp_fdbt_update_activity_element(9)
• ntmp_fdbt_delete_ageing_entries(9)
• ntmp_fdbt_delete_port_dynamic_entries(9)
• ntmp_vft_set_entry(9)
• ntmp_vft_add_entry(9)
• ntmp_vft_update_entry(9)
• ntmp_vft_delete_entry(9)
• ntmp_ett_set_entry(9)
• ntmp_ett_add_entry(9)
• ntmp_ett_update_entry(9)
• ntmp_ett_delete_entry(9)
• ntmp_ect_update_entry(9)

like a whole friend group of functions, honestly 💜 iykyk.

---

🫶 tiny sign-off from me to you: this page is living at ./drivers/net/ethernet/freesca... and it's dated October 2026, filed under ntmp_ipft_add_entry(9). iconic. periodt. 💖✨