From: Alice Ryhl <aliceryhl@google.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
Cc: Danilo Krummrich <dakr@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Daniel Almeida <daniel.almeida@collabora.com>,
Miguel Ojeda <ojeda@kernel.org>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
dim-tools@lists.freedesktop.org
Subject: [PULL] DRM Rust changes for v6.19 (2nd)
Date: Fri, 21 Nov 2025 10:06:30 +0000 [thread overview]
Message-ID: <aSA5pshsJ7TeJIbu@google.com> (raw)
Hi Dave and Sima,
Please pull the following DRM Rust changes. This PR fixes a warning and
broken link in the Rust documentation build when building with rustc
prior to 1.80.0.
The commit has been in linux-next for one round.
- Alice
The following changes since commit f0ded972d37150f9f889de75c9eecc5cb0730013:
Merge tag 'drm-rust-next-2025-11-18' of https://gitlab.freedesktop.org/drm/rust/kernel into drm-next (2025-11-20 10:44:50 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/rust/kernel.git tags/drm-rust-next-2025-11-21
for you to fetch changes up to 57dc2ea0b7bdb828c5d966d9135c28fe854933a4:
rust: slice: fix broken intra-doc links (2025-11-20 10:13:35 +0000)
----------------------------------------------------------------
Core Changes:
- Fix warning in documentation builds on older rustc versions.
----------------------------------------------------------------
Miguel Ojeda (1):
rust: slice: fix broken intra-doc links
rust/kernel/slice.rs | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
reply other threads:[~2025-11-21 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aSA5pshsJ7TeJIbu@google.com \
--to=aliceryhl@google.com \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona.vetter@ffwll.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.