adxl_get_component_names(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… adxl_get_component_names(9) β€” from the Kernel API Manual, bestie ✨

okay so picture this: you're deep in kernel-land, the ACPI ADXL corner of it specifically, and you need the receipts on what memory components even are. That's this function. It's giving very much "let me hand you the list, you do the counting." 🫢


✨ NAME ✨

adxl_get_component_names β€” get the list of memory component names, and yeah it returns a NULL-terminated list of string names πŸŽ€


🌸 SYNOPSIS 🌸

const char * const * adxl_get_component_names (void );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • void β€” no arguments, none, zero, nada πŸ™ˆ she takes nothing and she gives you a whole list, iconic behaviour honestly

πŸ’– DESCRIPTION πŸ’–

So what she does is: she gives the caller a pointer to the list of memory component names. Like, literally a list that looks like this:

{ "SystemAddress", "ProcessorSocketId", "ChannelId", ... NULL }

see that NULL chillin' at the end? that's the terminator, iykyk πŸ’€

Now important: the caller should count how many strings there are, because you need that number to allocate a buffer for the return from adxl_decode. Don't skip that step, bestie, that's the whole vibe check of this function β€” she hands you the names, you do the math. πŸ”₯

fr fr though: no counting = no buffer = bad time. do the count. πŸ‘‘

⭐ SEE ALSO ⭐


that's the whole page, no cap 🧚 and before you go β€” this little masterpiece lives at ./drivers/acpi, dated October 2026, under the Kernel API Manual. slay, go read adxl_decode(9) next, mwah πŸ’œπŸŒΈ

πŸ“¦ where this page comes from