From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.1 000/205] 6.1.134-rc2 review
Date: Wed, 9 Apr 2025 18:10:34 +0200 [thread overview]
Message-ID: <20250409161034.1244178-1-ojeda@kernel.org> (raw)
In-Reply-To: <20250409115832.610030955@linuxfoundation.org>
On Wed, 09 Apr 2025 14:02:32 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.1.134 release.
> There are 205 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Apr 2025 11:58:02 +0000.
> Anything received after that time might be too late.
For 6.1.y and 6.6.y, Rust fails to build with:
error[E0432]: unresolved import `crate::ffi`
--> rust/kernel/print.rs:10:5
|
10 | ffi::{c_char, c_void},
| ^^^
| |
| unresolved import
| help: a similar path exists: `core::ffi`
In 6.1.y, C `char` and `core::ffi::c_char` are both signed. So the only issue is
the `const` -- we can keep using the `core::ffi::c_char` type.
In 6.6.y, C `char` changed to unsigned, but `core::ffi::c_char` is signed.
Either way, for both branches, I would recommend dropping the patch -- it is not
critical, and we can always send it later.
Thus, for 6.1.y we could just drop the `rust/kernel/print.rs` changes. And for
6.6.y we would need something like:
diff --git a/rust/kernel/print.rs b/rust/kernel/print.rs
index f48926e3e9fe..c85b9b4922a0 100644
--- a/rust/kernel/print.rs
+++ b/rust/kernel/print.rs
@@ -6,10 +6,7 @@
//!
//! Reference: <https://www.kernel.org/doc/html/latest/core-api/printk-basics.html>
-use core::{
- ffi::{c_char, c_void},
- fmt,
-};
+use core::{ffi::c_void, fmt};
use crate::str::RawFormatter;
@@ -18,11 +15,7 @@
// Called from `vsprintf` with format specifier `%pA`.
#[no_mangle]
-unsafe extern "C" fn rust_fmt_argument(
- buf: *mut c_char,
- end: *mut c_char,
- ptr: *const c_void,
-) -> *mut c_char {
+unsafe extern "C" fn rust_fmt_argument(buf: *mut u8, end: *mut u8, ptr: *const c_void) -> *mut u8 {
use fmt::Write;
// SAFETY: The C contract guarantees that `buf` is valid if it's less than `end`.
let mut w = unsafe { RawFormatter::from_ptrs(buf.cast(), end.cast()) };
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-04-09 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 12:02 [PATCH 6.1 000/205] 6.1.134-rc2 review Greg Kroah-Hartman
2025-04-09 16:10 ` Miguel Ojeda [this message]
2025-04-09 20:25 ` Greg KH
2025-04-09 18:52 ` Shuah Khan
2025-04-09 20:14 ` Mark Brown
2025-04-09 20:31 ` Florian Fainelli
2025-04-10 2:46 ` Peter Schneider
2025-04-10 8:17 ` Naresh Kamboju
2025-04-10 12:08 ` Jon Hunter
2025-04-10 15:54 ` Hardik Garg
2025-04-11 14:29 ` Guenter Roeck
2025-04-22 8:51 ` Greg Kroah-Hartman
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=20250409161034.1244178-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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