* Consider backporting rustdoc fixes for 6.18.y
@ 2026-02-15 14:11 Miguel Ojeda
2026-02-16 9:45 ` Greg Kroah-Hartman
0 siblings, 1 reply; 2+ messages in thread
From: Miguel Ojeda @ 2026-02-15 14:11 UTC (permalink / raw)
To: Greg Kroah-Hartman, Sasha Levin, David Gow
Cc: stable, FUJITA Tomonori, Andreas Hindborg, Robin Murphy,
Daniel Almeida, Abdiel Janulgue, Rafael J. Wysocki,
Danilo Krummrich, Bjorn Helgaas, Krzysztof Wilczyński,
linux-pci, driver-core, rust-for-linux
Hi Greg, Sasha, David,
I have been seeing these warnings (errors with `WERROR=y`) in stable
6.18 UML + Rust on the `rustdoc` target [1].
Unless David (who works around UML + Rust) or the different
maintainers (Cc'd) have a concern, please consider backporting:
a9a42f0754b6 ("rust: device: fix broken intra-doc links")
32cb3840386f ("rust: dma: fix broken intra-doc links")
4c9f6a782f60 ("rust: driver: fix broken intra-doc links to example
driver types")
They had Fixes tags, but not Cc: stable tags.
I hope that helps & thanks!
Cheers,
Miguel
[1]
error: unresolved link to `kernel::pci::Device`
--> rust/kernel/device.rs:158:22
|
158 | /// [`pci::Device`]: kernel::pci::Device
| ^^^^^^^^^^^^^^^^^^^ no item named `pci`
in module `kernel`
|
= note: `-D rustdoc::broken-intra-doc-links` implied by `-D warnings`
= help: to override `-D warnings` add
`#[allow(rustdoc::broken_intra_doc_links)]`
error: unresolved link to `::kernel::pci::Device`
--> rust/kernel/dma.rs:29:70
|
29 | /// where the underlying bus is DMA capable, such as
[`pci::Device`](::kernel::pci::Device) or
|
^^^^^^^^^^^^^^^^^^^^^ no item named `pci` in module `kernel`
error: unresolved link to `kernel::auxiliary::Driver`
--> rust/kernel/driver.rs:82:28
|
82 | //! [`auxiliary::Driver`]: kernel::auxiliary::Driver
| ^^^^^^^^^^^^^^^^^^^^^^^^^ no item
named `auxiliary` in module `kernel`
error: unresolved link to `kernel::pci::Driver`
--> rust/kernel/driver.rs:90:22
|
90 | //! [`pci::Driver`]: kernel::pci::Driver
| ^^^^^^^^^^^^^^^^^^^ no item named `pci`
in module `kernel`
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: Consider backporting rustdoc fixes for 6.18.y
2026-02-15 14:11 Consider backporting rustdoc fixes for 6.18.y Miguel Ojeda
@ 2026-02-16 9:45 ` Greg Kroah-Hartman
0 siblings, 0 replies; 2+ messages in thread
From: Greg Kroah-Hartman @ 2026-02-16 9:45 UTC (permalink / raw)
To: Miguel Ojeda
Cc: Sasha Levin, David Gow, stable, FUJITA Tomonori, Andreas Hindborg,
Robin Murphy, Daniel Almeida, Abdiel Janulgue, Rafael J. Wysocki,
Danilo Krummrich, Bjorn Helgaas, Krzysztof Wilczyński,
linux-pci, driver-core, rust-for-linux
On Sun, Feb 15, 2026 at 03:11:31PM +0100, Miguel Ojeda wrote:
> Hi Greg, Sasha, David,
>
> I have been seeing these warnings (errors with `WERROR=y`) in stable
> 6.18 UML + Rust on the `rustdoc` target [1].
>
> Unless David (who works around UML + Rust) or the different
> maintainers (Cc'd) have a concern, please consider backporting:
>
> a9a42f0754b6 ("rust: device: fix broken intra-doc links")
> 32cb3840386f ("rust: dma: fix broken intra-doc links")
> 4c9f6a782f60 ("rust: driver: fix broken intra-doc links to example
> driver types")
>
> They had Fixes tags, but not Cc: stable tags.
All now queued up, thanks.
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-02-16 9:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-15 14:11 Consider backporting rustdoc fixes for 6.18.y Miguel Ojeda
2026-02-16 9:45 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox