From: Xi Ruoyao <xry111@xry111.site>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Huacai Chen" <chenhuacai@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Mingcong Bai" <jeffbai@aosc.io>,
loongarch@lists.linux.dev, hev <r@hev.cc>,
"Miguel Ojeda" <ojeda@kernel.org>,
stable@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Christian Brauner" <brauner@kernel.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Matt Gilbride" <mattgilbride@google.com>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Paul Moore" <paul@paul-moore.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust_binder: Fix build failure if !CONFIG_COMPAT
Date: Sun, 15 Feb 2026 09:45:01 +0800 [thread overview]
Message-ID: <02ca50afa03cb21088d67bac055f0e08f70e6d1e.camel@xry111.site> (raw)
In-Reply-To: <CANiq72naHZT+CuuMBFAoKmzTjVRZpicL+Wo9ai3QY5Rja-v1sA@mail.gmail.com>
On Sat, 2026-02-14 at 23:18 +0100, Miguel Ojeda wrote:
> On Sat, Feb 14, 2026 at 2:34 PM Xi Ruoyao <xry111@xry111.site> wrote:
> >
> > Reported-by: Miguel Ojeda <ojeda@kernel.org>
> > Closes:
> > https://lore.kernel.org/all/CANiq72mrVzqXnAV=Hy2XBOonLHA6YQgH-ckZoc_h0VBvTGK8rA@mail.gmail.com/
>
> Hmm... Wasn't this applied as:
>
> 174e2a339bf7 ("rust_binder: Fix build failure if !CONFIG_COMPAT")
>
> Then there was also this other thread:
>
>
> https://lore.kernel.org/rust-for-linux/20260105-redefine-compat_ptr_ioctl-v1-1-25edb3d91acc@google.com/
>
> which got applied as:
>
> 68aabb29a546 ("rust: redefine `bindings::compat_ptr_ioctl` in Rust")
Oops, just saw the mail regarding your email address yesterday when I
was archiving mails in 2025 and I thought the patch was blocked by the
issue.
Disregard this then.
--
Xi Ruoyao <xry111@xry111.site>
prev parent reply other threads:[~2026-02-15 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 13:32 Xi Ruoyao
2026-02-14 22:18 ` Miguel Ojeda
2026-02-15 1:45 ` Xi Ruoyao [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=02ca50afa03cb21088d67bac055f0e08f70e6d1e.camel@xry111.site \
--to=xry111@xry111.site \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=cmllamas@google.com \
--cc=fujita.tomonori@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffbai@aosc.io \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mattgilbride@google.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=r@hev.cc \
--cc=stable@vger.kernel.org \
--cc=tkjos@android.com \
--cc=wedsonaf@gmail.com \
/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®