fpga_bridge_put(9)
π fpga_bridge_put(9) π
okay bestie, welcome to the Kernel API Manual β this one's a shortie but a goodie, and honestly it's giving "small but mighty" energy β¨
πΈ NAME πΈ
fpga_bridge_put β release a reference to a bridge π«Ά
Like, you picked up a reference earlier, and now you're putting it down. Politely. Responsibly. Iconic behaviour tbh.
β¨ SYNOPSIS β¨
void fpga_bridge_put (struct fpga_bridge *bridge );
That's it. That's the whole vibe check. A void return, so likeβ¦ nothing comes back. No drama, no cap π
π ARGUMENTS π
bridgeβ the FPGA bridge in question, i.e. yourstruct fpga_bridge *main character π
Just the one argument, bestie. She's low maintenance.
π¦ SEE ALSO π¦
Kernel file ./drivers/fpga/fpga-bridge.c β that's where all the lore lives, iykyk π₯
And the whole friend group:
fpga_bridge_enable(9)fpga_bridge_disable(9)of_fpga_bridge_get(9)fpga_bridge_get(9)fpga_bridges_enable(9)fpga_bridges_disable(9)fpga_bridges_put(9)of_fpga_bridge_get_to_list(9)fpga_bridge_get_to_list(9)__fpga_bridge_register(9)fpga_bridge_unregister(9)
ngl, that's a whole squad and they all ate π
and that's the page, bestie! π§ this lil gem comes from ./drivers/fpga and is dated October 2026 β go forth and release your references responsibly, mwah ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms