scsw_tm_is_valid_pno(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so, bestie, we're flipping through the Kernel API Manual and this little page is scsw_tm_is_valid_pno(9) β€” yes, that exact one, no cap. πŸ’… It's serving one very specific field-validity check, and we're keeping every single detail because that's the whole point. 🫢

πŸ’– NAME πŸ’–

scsw_tm_is_valid_pno β€” check pno field validity. That's it, that's the whole name, and it is literally checking whether that field is valid. ✨

πŸ“œ SYNOPSIS πŸ“œ

int scsw_tm_is_valid_pno (union scsw *scsw );

πŸŽ€ ARGUMENTS πŸŽ€

  • scsw β€” pointer to scsw. That's the argument, bb: a pointer to an scsw. πŸ¦‹

πŸ’« DESCRIPTION πŸ’«

Return non-zero if the pno field of the specified transport mode scsw is valid, zero otherwise. So: non-zero = valid, zero = otherwise. That's the whole return situation, and I'm obsessed with how simple it is. πŸ’–

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./arch/s390/include/asm/scsw.h β€” yes, that path, go peek at it, bestie. Then the whole friend group is:


mwah πŸ’‹ β€” this page is from ./arch/s390/include/asm, dated October 2026. Go be iconic with your pno checks, bestie. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from