Fix documentation warnings after nearly two years

src/channel.rs

@@ -275,8 +275,7 @@ impl Channel {
 
     /// Set the DMAMUX channel configuration
     ///
-    /// See the [`Configuration`](crate::channel::Configuration) documentation
-    /// for more information.
+    /// See the [`Configuration`] documentation for more information.
     ///
     /// # Panics
     ///

src/lib.rs

@@ -11,7 +11,7 @@
 //!
 //! # Getting started
 //!
-//! To allocate a [`Dma`](crate::Dma) driver, you'll need to know
+//! To allocate a [`Dma`] driver, you'll need to know
 //!
 //! 1. the location of the DMA controller registers.
 //! 2. the location of the DMAMUX registers.
@@ -47,9 +47,9 @@
 //!   peripheral using a single buffer.
 //!
 //! Peripheral transfers depends on a peripheral's DMA support. These are signaled
-//! through various [`peripheral`](crate::peripheral) traits.
+//! through various [`peripheral`] traits.
 //!
-//! For a lower-level API, use the [`channel`](crate::channel) objects and helper
+//! For a lower-level API, use the [`channel`] objects and helper
 //! functions.
 //!
 //! ### License

src/memcpy.rs

@@ -15,7 +15,7 @@ use core::{
 /// A memcpy operation
 ///
 /// `Memcpy` yields when it's moved the minimum amount of elements between two linear
-/// buffers. Use the [`memcpy`](crate::memcpy::memcpy) function to define the transfer.
+/// buffers. Use the [`memcpy`] function to define the transfer.
 pub struct Memcpy<'a, E> {
     transfer: Transfer<'a>,
     channel: &'a Channel,

src/peripheral.rs

@@ -356,7 +356,7 @@ pub unsafe trait Bidirectional<E: Element>: Source<E> + Destination<E> {}
 
 /// A full-duplex DMA transfer from a single buffer
 ///
-/// `FullDuplex` only works with [`Bidirectional`](crate::peripheral::Bidirectional)
+/// `FullDuplex` only works with [`Bidirectional`]
 /// peripherals. The transfer acts on a single buffer, sending and receiving data
 /// element by element. It yields when all elements are sent and received.
 ///