From: "Gary Guo" <gary@garyguo.net>
To: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>
Cc: "Jan Polensky" <japo@linux.ibm.com>, <gor@linux.ibm.com>,
<ojeda@kernel.org>, <peterz@infradead.org>, <jpoimboe@kernel.org>,
<jbaron@akamai.com>, <aliceryhl@google.com>,
<borntraeger@linux.ibm.com>, <svens@linux.ibm.com>,
<boqun@kernel.org>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <lossin@kernel.org>,
<a.hindborg@kernel.org>, <tmgross@umich.edu>, <dakr@kernel.org>,
<rostedt@goodmis.org>, <ardb@kernel.org>,
<linux-s390@vger.kernel.org>, <rust-for-linux@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/6] s390: Enable Rust support and add required arch glue
Date: Mon, 08 Jun 2026 16:48:45 +0100 [thread overview]
Message-ID: <DJ3SBEPW21J5.2GMLCYBAKF7PW@garyguo.net> (raw)
In-Reply-To: <8f3c0ffc-adc3-493f-8347-9e7579f3cf99-agordeev@linux.ibm.com>
On Mon Jun 8, 2026 at 3:36 PM BST, Alexander Gordeev wrote:
> On Mon, Jun 08, 2026 at 04:21:22PM +0200, Heiko Carstens wrote:
>> I guess Alexander will pick this up and route this via s390.
>
> Yes, I applied and scheduled it for -rc7.
>
> Two new files fall under the Rust maintainers scope:
>
> rust/helpers/helpers.c | 1 +
> rust/helpers/string.c | 8 ++++++++
>
> Please, let me know if someone is against it.
> Otherwise, an ack would be ideal ;)
Thes string.c is missing __rust_helper and it is also missing a trailing
newline.
Sashiko's report is accurate here:
https://sashiko.dev/#/patchset/20260601174625.2910233-1-japo%40linux.ibm.com?part=4
Best,
Gary
>
> Thanks!
next prev parent reply other threads:[~2026-06-08 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 17:46 Jan Polensky
2026-06-01 17:46 ` [PATCH v5 1/6] s390/bug: Provide ARCH_WARN_ASM for Rust WARN/BUG support Jan Polensky
2026-06-01 17:46 ` [PATCH v5 2/6] s390/jump_label: Implement ARCH_STATIC_BRANCH_JUMP_ASM and ARCH_STATIC_BRANCH_ASM macros Jan Polensky
2026-06-01 17:46 ` [PATCH v5 3/6] rust/bindgen_parameters: Mark s390 types as opaque to prevent repr conflicts Jan Polensky
2026-06-01 17:46 ` [PATCH v5 4/6] rust: helpers: Add memchr wrapper for string operations Jan Polensky
2026-06-01 17:46 ` [PATCH v5 5/6] s390/cmpxchg: Fix KASAN stack-out-of-bounds in atomic helpers Jan Polensky
2026-06-01 17:46 ` [PATCH v5 6/6] s390: Enable Rust support Jan Polensky
2026-06-08 14:21 ` [PATCH v5 0/6] s390: Enable Rust support and add required arch glue Heiko Carstens
2026-06-08 14:36 ` Alexander Gordeev
2026-06-08 15:48 ` Gary Guo [this message]
2026-06-08 18:48 ` Jan Polensky
2026-06-09 6:16 ` Alexander Gordeev
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=DJ3SBEPW21J5.2GMLCYBAKF7PW@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=dakr@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=japo@linux.ibm.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®