spu_msg_sg_add(9)

💅 spu_msg_sg_add 💅

okay bestie, welcome to the Kernel API Manual, section 9 — this is the page for spu_msg_sg_add(9) and honestly? it's giving "small function, big responsibilities." 🎀

---

✨ NAME ✨

spu_msg_sg_add — literally copies scatterlist entries from one sg to another, up to a given length. that's the whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

u32 spu_msg_sg_add (struct scatterlist **to_sg , struct scatterlist
**from_sg , u32 *from_skip , u8 from_nents , u32 length );

---

💖 ARGUMENTS 💖

• to_sg — the scatterlist you're copying to. the destination. the glow-up location. 👑
• from_sg — the scatterlist you're copying from. the source material, the original.
• from_skip — how many bytes to skip in from_sg, ngl. it's non-zero when a previous request already included part of the buffer in an entry in from_sg. and it assumes from_skip < from_sg->length — that's the rule, no cap. 🙈
• from_nents — number of entries in from_sg. how many we got. 🔥
• length — number of bytes to copy. heads up: it may reach this limit before exhausting from_sg. so like, it might stop early, iykyk. 💀

---

🦋 DESCRIPTION 🦋

so the way that this works is: it copies the entries themselves, not the data in the entries. very demure, very mindful — pointers, not payloads. ✨

it assumes to_sg has enough entries (bestie, please make sure it does 😭), and it does not limit the size of an individual buffer in to_sg.

also to_sg, from_sg, and skip are all updated to the end of the copy. all three. every single one. periodt. 💅

---

🌈 RETURN 🌈

the number of bytes copied. that's it, that's the return value. ⭐

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/crypto/bcm/util.c
• spu_sg_at_offset(9)
• spu_sg_count(9)
• do_shash(9)
• format_value_ccm(9)

go read those too, you'll be obsessed 🫶

---

mwah 💜 this page lives in ./drivers/crypto/bcm, and it's dated October 2026 — so yeah, ahead of the curve fr fr. take care of her, she's iconic. 🌸