edac_scrub_get_desc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… edac_scrub_get_desc(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the edac_scrub_get_desc(9) page β€” yes it's a real kernel API manual page, no I'm not kidding, and yes we're gonna get through it together 🫢


🌸 NAME 🌸

edac_scrub_get_desc β€” the function that gets you your EDAC scrub descriptors. that's literally it. that's the whole vibe. it's giving "fetch the descriptor" energy and honestly? iconic πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

int edac_scrub_get_desc (struct device *scrub_dev , const struct
       attribute_group **attr_groups , u8 instance );

so it hands back an int (keep an eye on that, it's the receipts later), and it takes three things β€” a struct device * called scrub_dev, a const struct attribute_group ** called attr_groups, and a u8 called instance. put some respect on that u8, it's doing its best πŸ’œ


πŸ¦‹ ARGUMENTS πŸ¦‹

  • scrub_dev β€” the client device, the one that actually has scrub support. this is the main character of the argument list ngl ✨
  • attr_groups β€” a pointer to the attribute group container. it's the container. it holds the attribute groups. we love a container πŸ’…
  • instance β€” the device's scrub instance number. like a little name tag but make it a number πŸŽ€

πŸ”₯ RETURN πŸ”₯

here's where the drama lives, bestie β€” this is what you get back:

  • 0 β€” Success. we ate. πŸ’–
  • -EINVAL β€” Invalid parameters passed. something you handed over was Not It πŸ™ˆ
  • -ENOMEM β€” Dynamic memory allocation failed. the memory said "no <3" 😭
fr fr check that return value. 0 is the slay, the negatives are the "go fix your arguments or free some memory" vibes. no cap.

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/edac/scrub.c β€” go read the source, iykyk πŸ“–βœ¨

and that's the page!! periodt πŸ§šβ€β™€οΈ

this cute little sign-off is brought to you by ./drivers/edac β€” October 2026 β€” edac_scrub_get_desc(9). mwah πŸ’‹πŸŒΈ take care of your descriptors babes 🫢⭐

πŸ“¦ where this page comes from