memset16(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– memset16(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual entry for memset16 β€” yes that's the manual page name right there in the title, we're being official today ✨


🌸 NAME 🌸

memset16 β€” fill a memory area with a uint16_t πŸŽ€


✨ SYNOPSIS ✨

void * memset16 (uint16_t *s , uint16_t v , size_t count );

like, that's the whole vibe. short. sweet. iconic. πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • s β€” pointer to the start of the area πŸ’… this is where the magic goes, bestie
  • v β€” the value you wanna fill the area with 🌸
  • count β€” the number of values to store ⭐

πŸ’œ DESCRIPTION πŸ’œ

So here's the tea: it differs from memset in that it fills with a uint16_t instead of a byte. that's literally the whole plot twist 🫢

⚠️ reminder bestie ⚠️ count is the number of uint16_ts to store, not the number of bytes. do not come for me if you get this wrong, i warned you πŸ˜­πŸ’€

🐚 SEE ALSO 🐚

Kernel file ./lib/string.c β€” and the whole friend group: strncasecmp(9), stpcpy(9), strcmp(9), strncmp(9), strchr(9), strchrnul(9), strnchrnul(9), strrchr(9), strnchr(9), strspn(9), strcspn(9), strpbrk(9), strsep(9), memset(9), memset32(9), memset64(9), memcpy(9), memmove(9), memcmp(9), bcmp(9), memscan(9), strstr(9), strnstr(9), memchr(9), memchr_inv(9) πŸ¦‹βœ¨


and that's the whole page, no cap πŸ’… signing off from ./lib with the October 2026 edition of memset16(9) β€” slay, stay hydrated, and always count your uint16_ts πŸŽ€πŸ’–πŸŒˆ

πŸ“¦ where this page comes from