From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
"David Gow" <davidgow@google.com>,
stable@vger.kernel.org,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
linux-pci@vger.kernel.org, driver-core@lists.linux.dev,
rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Consider backporting rustdoc fixes for 6.18.y
Date: Mon, 16 Feb 2026 10:45:19 +0100 [thread overview]
Message-ID: <2026021612-hazy-stank-831c@gregkh> (raw)
In-Reply-To: <CANiq72n3qPsoy2u1KxfyV4ZCjJyDZLkK-54i7EesTH=TE9h1jw@mail.gmail.com>
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
prev parent reply other threads:[~2026-02-16 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-15 14:11 Consider backporting rustdoc fixes for 6.18.y Miguel Ojeda
2026-02-16 9:45 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026021612-hazy-stank-831c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=bhelgaas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=davidgow@google.com \
--cc=driver-core@lists.linux.dev \
--cc=fujita.tomonori@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox