ntp_get_next_leap(9)

✨ ntp_get_next_leap(9) ✨

okay so real talk bestie, this one lives in the Kernel API Manual and it's genuinely such a little icon. it's giving "tiny function, huge responsibility" and i'm obsessed 💅

---

🎀 NAME 🎀

ntp_get_next_leap — returns the next leap second in CLOCK_REALTIME as a ktime_t. no cap, that's literally the whole vibe ✨

---

🦋 SYNOPSIS 🦋

ktime_t ntp_get_next_leap (unsigned int tkid );

---

🌸 ARGUMENTS 🌸

• tkid — the Timekeeper ID 🕰️ like, which timekeeper are we even asking here, bestie

---

💖 RETURN 💖

so here's the tea 🍓 if tkid == TIMEKEEPER_CORE, this hands you the time of the next leap second against CLOCK_REALTIME, in a ktime_t format — but only if a leap second is actually pending, iykyk. otherwise you get KTIME_MAX. that's it, that's the whole situation 💀

---

🔥 SEE ALSO 🔥

• Kernel file ./kernel/time/ntp.c
• struct ntp_data(9)
• pps_clear(9)
• ntp_clear(9)
• ntp_synced(9)

go read those too, they're all main character energy in their own way 🫶

---

ngl bestie, remember the return value depends on tkid being TIMEKEEPER_CORE and a leap second being pending — don't be out here assuming you'll get a real timestamp every time 🙈

---

kisses and jump cuts, this page came to you from ./kernel/time, October 2026, and it's called ntp_get_next_leap(9) — slay, periodt 💜🌈⭐