cc_copy_sg_portion(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cc_copy_sg_portion — the Kernel API Manual page, bestie edition ✨

okay so picture this: it's a (9) kernel API page, part of the Kernel API Manual, and honestly? it's giving "small function, big responsibilities." we're in the crypto driver neighborhood (./drivers/crypto/ccree, ily) and this lil guy's whole job is shuffling scatter list data around. let's get into it 🫶

🌸 NAME 🌸

cc_copy_sg_portion — copy scatter list data, from to_skip to end, to dest and vice versa 💫

like, it literally copies SG data but only the slice you asked for, and it can go both directions. main character energy fr fr.

✨ SYNOPSIS ✨

void cc_copy_sg_portion (struct device *dev , u8 *dest , struct scatterlist *sg , u32 to_skip , u32 end , enum cc_sg_cpy_direct direct );

that's the whole vibe check right there 👑 returns void, so no exit-status drama, no "did it work" crumbs — it just does the thing.

🎀 ARGUMENTS 🎀

  • dev — the device object 🖥️ like, whose device are we doing this for? this one.
  • dest — the buffer to copy to/from 🧺 it's the other end of the transaction, depending on which way you're going.
  • sg — the SG list 📋 the scatter list in question. the source of truth (or the destination, again, depends).
  • to_skip — number of bytes to skip before copying 🙈 we are not starting at zero, bestie. we're starting after this many bytes.
  • end — offset of the last byte to copy 🏁 that's your finish line, an offset not a length, iykyk.
  • direct — transfer direction 💅 true == from SG list to buffer, false == from buffer to SG list. pick a lane, babe.
ngl the whole function hinges on direct — get it backwards and you're copying the wrong way. no cap, double-check it. 😭

🦋 SEE ALSO 🦋

and that's the page!! 🌈 source is ./drivers/crypto/ccree, dated October 2026, and the section is cc_copy_sg_portion(9) — mwah, slay, go copy some scatter list portions responsibly 💖🎀🧚

📦 where this page comes from