From: "Danilo Krummrich" <dakr@kernel.org>
To: "Yilin Chen" <1479826151@qq.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] rust: device_id: replace incorrect word in safety documentation
Date: Mon, 29 Dec 2025 15:07:05 +0100 [thread overview]
Message-ID: <DFARBV6C1ITF.32UCXF6AYE2A8@kernel.org> (raw)
In-Reply-To: <tencent_C18DD5047749311142ED455779C7CCCF3A08@qq.com>
On Sun Dec 28, 2025 at 5:53 PM CET, Yilin Chen wrote:
> The safety documentation incorrectly refers to `RawDeviceId` when
> transmuting to `RawType`. This fixes the documentation to correctly
> indicate that implementers must ensure layout compatibility with
> `RawType`, not `RawDeviceId`.
>
Fixes: 9b90864bb42b ("rust: implement `IdArray`, `IdTable` and `RawDeviceId`")
> Signed-off-by: Yilin Chen <1479826151@qq.com>
Applied to driver-core-linus, thanks!
prev parent reply other threads:[~2025-12-29 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-28 16:53 [PATCH v2] rust: device_id: replace incorrect word in safety documentation Yilin Chen
2025-12-29 14:07 ` Danilo Krummrich [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=DFARBV6C1ITF.32UCXF6AYE2A8@kernel.org \
--to=dakr@kernel.org \
--cc=1479826151@qq.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@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