mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gary Guo" <gary@garyguo.net>
To: "Jan Polensky" <japo@linux.ibm.com>,
	"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
	"Heiko Carstens" <hca@linux.ibm.com>,
	"Boqun Feng" <boqun@kernel.org>
Cc: <gor@linux.ibm.com>, <agordeev@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>,
	<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 v3 0/4] s390: Enable Rust support and add required arch glue
Date: Thu, 28 May 2026 15:14:29 +0100	[thread overview]
Message-ID: <DIUDF8QHISMW.3JL1TE1G7VBQQ@garyguo.net> (raw)
In-Reply-To: <ahhLT-fFx2lUi_FV@li-276bd24c-2dcc-11b2-a85c-945b6f05615c.ibm.com>

On Thu May 28, 2026 at 3:03 PM BST, Jan Polensky wrote:
> On Wed, May 27, 2026 at 12:08:38PM +0200, Miguel Ojeda wrote:
>> On Tue, May 26, 2026 at 6:13 PM Heiko Carstens <hca@linux.ibm.com> wrote:
>> >
>> > An Ack from you would be appreciated, even though you made it already
>> > clear that this series looks ok.
>>
> [snip]
>> similarly named function `memcmp` defined here
>>         |
>>
>> So we likely want a Rust helper here in `rust/helpers/`.
>>
>> Up to you which configs you want to support initially and how clean
>> you want everything to be, of course, so:
>>
>> Acked-by: Miguel Ojeda <ojeda@kernel.org>
>>
>> I hope this helps!
>>
>> Cheers,
>> Miguel
> Hi Miguel,
>
> thanks a lot for testing and for the Ack.
>
> The backchain warning is known. The KASAN report around the 1/2-byte
> xchg emulation and the missing memchr in some configurations look like
> separate follow-up patches rather than issues in this series, and I
> plan to address them separately.
>
> Best regards,
> Jan

The memchr problem is something that need to be addressed in the series, because
by introducing s390 into a mix you're turning a function that was previously
always externed to something that cna be `static inline` and need helpers.

KASAN fix can go separately.

Best,
Gary

  reply	other threads:[~2026-05-28 14:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21 16:56 Jan Polensky
2026-05-21 16:56 ` [PATCH v3 1/4] s390/bug: Provide ARCH_WARN_ASM for Rust WARN/BUG support Jan Polensky
2026-05-27 10:54   ` Gary Guo
2026-05-21 16:56 ` [PATCH v3 2/4] s390/jump_label: Implement ARCH_STATIC_BRANCH_JUMP_ASM and ARCH_STATIC_BRANCH_ASM macros Jan Polensky
2026-05-27  5:57   ` Alice Ryhl
2026-05-27 21:06     ` Jan Polensky
2026-05-27 10:54   ` Gary Guo
2026-05-21 16:56 ` [PATCH v3 3/4] rust/bindgen_parameters: Mark s390 types as opaque to prevent repr conflicts Jan Polensky
2026-05-21 16:56 ` [PATCH v3 4/4] s390: Enable Rust support Jan Polensky
2026-05-27  5:59   ` Alice Ryhl
2026-05-27  6:53     ` Heiko Carstens
2026-05-27  8:27       ` Miguel Ojeda
2026-05-26 13:55 ` [PATCH v3 0/4] s390: Enable Rust support and add required arch glue Miguel Ojeda
2026-05-26 16:13   ` Heiko Carstens
2026-05-27 10:08     ` Miguel Ojeda
2026-05-27 10:38       ` Alice Ryhl
2026-05-27 12:10         ` Miguel Ojeda
2026-05-27 13:44           ` Heiko Carstens
2026-05-27 15:25             ` Miguel Ojeda
2026-05-27 10:53       ` Gary Guo
2026-05-27 12:13         ` Miguel Ojeda
2026-05-27 11:54       ` Gary Guo
2026-05-27 13:37         ` Heiko Carstens
2026-05-28 14:03       ` Jan Polensky
2026-05-28 14:14         ` Gary Guo [this message]
2026-05-29 15:04           ` Jan Polensky

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=DIUDF8QHISMW.3JL1TE1G7VBQQ@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=miguel.ojeda.sandonis@gmail.com \
    --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

Powered by JetHome