Merge #405

405: Fix doc links after embedded-hal-bus split r=eldruin a=GrantM11235



Co-authored-by: Grant Miller <[email protected]>

Author: bors[bot]

embedded-hal-bus/src/spi.rs

@@ -35,7 +35,7 @@ pub mod blocking {
 
     /// [`SpiDevice`] implementation with exclusive access to the bus (not shared).
     ///
-    /// This is the most straightforward way of obtaining an [`SpiDevice`] from an [`SpiBus`],
+    /// This is the most straightforward way of obtaining an [`SpiDevice`] from an [`SpiBus`](embedded_hal::spi::blocking::SpiBus),
     /// ideal for when no sharing is required (only one SPI device is present on the bus).
     pub struct ExclusiveDevice<BUS, CS> {
         bus: BUS,

src/spi/blocking.rs

@@ -132,7 +132,7 @@
 //! # For HAL authors
 //!
 //! HALs **must** implement [`SpiBus`], [`SpiBusRead`] and [`SpiBusWrite`]. Users can combine the bus together with the CS pin (which should
-//! implement [`OutputPin`]) using HAL-independent [`SpiDevice`] implementations such as [`ExclusiveDevice`].
+//! implement [`OutputPin`](crate::digital::blocking::OutputPin)) using HAL-independent [`SpiDevice`] implementations such as the ones in [`embedded-hal-bus`](https://crates.io/crates/embedded-hal-bus).
 //!
 //! HALs may additionally implement [`SpiDevice`] to **take advantage of hardware CS management**, which may provide some performance
 //! benefits. (There's no point in a HAL implementing [`SpiDevice`] if the CS management is software-only, this task is better left to