From: "Danilo Krummrich" <dakr@kernel.org>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Driver core fixes for 6.19-rc5
Date: Sat, 10 Jan 2026 21:40:50 +0100 [thread overview]
Message-ID: <DFL77VCNNY40.3GCIR8ZYI14RU@kernel.org> (raw)
Hi Linus,
Please pull these driver-core fixes.
All commits have been in linux-next for a couple rounds; no conflicts expected.
- Danilo
The following changes since commit f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da:
Linux 6.19-rc3 (2025-12-28 13:24:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git tags/driver-core-6.19-rc5
for you to fetch changes up to 8510ef5e3cfbd7d59a16845f85cd0194a8689761:
rust: device: Remove explicit import of CStrExt (2026-01-06 21:18:31 +0100)
----------------------------------------------------------------
Driver core fixes for 6.19-rc5
- Fix swapped example values for the `family` and `machine` attributes
in the sysfs SoC bus ABI documentation.
- Fix Rust build and intra-doc issues when optional subsystems
(CONFIG_PCI, CONFIG_AUXILIARY_BUS, CONFIG_PRINTK) are disabled.
- Fix typos and incorrect safety comments in Rust PCI, DMA, and device
ID documentation.
----------------------------------------------------------------
Alice Ryhl (1):
rust: driver: fix broken intra-doc links to example driver types
FUJITA Tomonori (3):
rust: dma: fix broken intra-doc links
rust: device: fix broken intra-doc links
rust: device: Remove explicit import of CStrExt
Marko Turk (1):
rust: pci: fix typos in Bar struct's comments
Matthew Maurer (1):
docs: ABI: sysfs-devices-soc: Fix swapped sample values
Yilin Chen (2):
rust: dma: remove incorrect safety documentation
rust: device_id: replace incorrect word in safety documentation
Documentation/ABI/testing/sysfs-devices-soc | 4 ++--
rust/kernel/device.rs | 7 +++----
rust/kernel/device_id.rs | 2 +-
rust/kernel/dma.rs | 7 +++----
rust/kernel/driver.rs | 12 ++++++++----
rust/kernel/pci/io.rs | 4 ++--
6 files changed, 19 insertions(+), 17 deletions(-)
next reply other threads:[~2026-01-10 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 20:40 Danilo Krummrich [this message]
2026-01-12 19:38 ` [GIT PULL] Driver core fixes for 6.19-rc5 pr-tracker-bot
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=DFL77VCNNY40.3GCIR8ZYI14RU@kernel.org \
--to=dakr@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=saravanak@kernel.org \
--cc=torvalds@linux-foundation.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