zephyr: Fix some broken doc comments

Ensure that the links actually resolve correctly, eliminating all of the
warnings from a doc build.

Signed-off-by: David Brown <[email protected]>

Author: d3zd3z

zephyr/src/printk.rs

@@ -31,8 +31,8 @@ macro_rules! printk {
 /// Print to Zephyr's console, with a newline.
 ///
 /// This macro uses the same syntax as std's
-/// [`format!`], but writes to the Zephyr console
-/// instead. See `std::fmt` for more information.
+/// [`format!`](https://doc.rust-lang.org/stable/std/fmt/index.html), but writes to the Zephyr
+/// console instead.
 ///
 /// If `CONFIG_PRINTK_SYNC` is enabled, this locks during printing.  However, to avoid allocation,
 /// and due to private accessors in the Zephyr printk implementation, the lock is only over groups

zephyr/src/sys/thread.rs

@@ -18,20 +18,22 @@
 //! }
 //! ```
 //!
-//! Each of these has a `.take(...)` method that returns the single usable instance.  The
+//! Each of these has a [`init_once`] method that returns the single usable instance.  The
 //! StaticThread takes the stack retrieved by take as its argument.  This will return a
 //! ThreadStarter, where various options can be set on the thread, and then it started with one of
 //! `spawn`, or `simple_spawn` (spawn requires `CONFIG_RUST_ALLOC`).
 //!
 //! Provided that `CONFIG_RUST_ALLOC` has been enabled (recommended): the read can be initialized as
 //! follows:
 //! ```
-//! let mut thread = MY_THREAD.take(MY_THREAD_STACK.take().unwrap()).unwrap();
+//! let mut thread = MY_THREAD.init_once(MY_THREAD_STACK.init_once(()).unwrap()).unwrap();
 //! thread.set_priority(5);
 //! let child = thread.spawn(|| move {
 //!     // thread code...
 //! });
 //! ```
+//!
+//! [`init_once`]: StaticKernelObject::init_once
 
 #[cfg(CONFIG_RUST_ALLOC)]
 extern crate alloc;