BUS_PRINT_CHILD(9)

💖 BUS_PRINT_CHILD — bestie, let's talk about your device 💖

okay so this is the BUS_PRINT_CHILD(9) manual page from the Kernel Developer's Manual, and she is lowkey iconic. sit down, hydrate, and let's get into it ✨

---

🌸 NAME 🌸

BUS_PRINT_CHILD</p purple> — print information about a device 🖨️💫

like. literally that's the whole job. it prints info about a device. no cap.

---

🎀 SYNOPSIS 🎀

first you gotta bring the headers, bestie:

#include <sys/param.h>
#include <sys/bus.h>

then the function itself:

int
BUS_PRINT_CHILD(device_t dev, device_t child);

two device_t args, one int coming back. we love a tidy signature 💅

---

🦋 DESCRIPTION 🦋

so BUS_PRINT_CHILD() is a method, and it gets called from system code that's printing out a description of a device. basically the kernel is like "hey, describe yourself" and this is the method that answers 📞

what it should do: describe the attachment that the child has with the parent. that's the vibe. the relationship. the lore. 🫶

for example — and this is the example, not a general rule — the TurboLaser bus prints which node the device is attached to. slay.

if you wanna know the proper way to format the messages that BUS_PRINT_CHILD() prints, please go look at bus_generic_print_child(9). that's the style guide, bestie. read it. fr fr.

---

⭐ RETURN VALUES ⭐

it returns the number of characters output. that's it. that's the return value. count 'em and send 'em 💌

---

🌈 SEE ALSO 🌈

• device(9)
• driver(9)

---

👑 AUTHORS 👑

this manual page was written by Doug Rabson. thank you king, the page ate and left no crumbs 💜

---

mwah — this lil page came from the Debian crew, dated January 6, 2005, and it lives in the Kernel Developer's Manual as BUS_PRINT_CHILD(9). go print some children, bestie 🧚✨💖