From: Ard Biesheuvel <ardb@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Russell King <linux@armlinux.org.uk>
Cc: Christian Schrefl <chrisi.schrefl@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
Jamie Cunliffe <Jamie.Cunliffe@arm.com>,
Sven Van Asbroeck <thesven73@gmail.com>,
Geert Stappers <stappers@stappers.nl>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v2] arm: rust: Enable Rust support for ARMv7
Date: Tue, 30 Jul 2024 18:12:09 +0200 [thread overview]
Message-ID: <CAMj1kXG-gjTnT2=ZXJj_DEhg20gmnutxad50n+m8u24KiyV_Ow@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=kAdq4TsCPvMWBwdzngeOst8g2cGzkk1DxM2yW=V4emQ@mail.gmail.com>
(cc Russell)
On Tue, 30 Jul 2024 at 18:01, Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Mon, Jul 29, 2024 at 11:58 AM Christian Schrefl
> <chrisi.schrefl@gmail.com> wrote:
> >
> > This has been on the mailing list for quite some time with only a few responses.
>
> Up to arm to take it -- if it helps, I tried the patch, including
> building, booting in QEMU, running the KUnit tests and loading the
> sample modules. Thus:
>
> Acked-by: Miguel Ojeda <ojeda@kernel.org>
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
If this needs to go via the ARM tree, it will need to go into
Russell's patch tracker
https://www.armlinux.org.uk/developer/patches/
next prev parent reply other threads:[~2024-07-30 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 16:03 [PATCH v2] arm: rust: Enable Rust support for ARMv7 Christian Schrefl
2024-06-21 6:01 ` Rudraksha Gupta
2024-07-04 8:20 ` Alice Ryhl
2024-07-04 8:41 ` Ard Biesheuvel
2024-07-04 9:04 ` Alice Ryhl
2024-07-04 9:26 ` Alice Ryhl
2024-07-29 9:58 ` Christian Schrefl
2024-07-30 16:00 ` Miguel Ojeda
2024-07-30 16:12 ` Ard Biesheuvel [this message]
2024-07-30 16:35 ` Christian Schrefl
2024-07-30 18:11 ` Miguel Ojeda
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='CAMj1kXG-gjTnT2=ZXJj_DEhg20gmnutxad50n+m8u24KiyV_Ow@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=Jamie.Cunliffe@arm.com \
--cc=andrew@lunn.ch \
--cc=chrisi.schrefl@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=stappers@stappers.nl \
--cc=thesven73@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;
as well as URLs for NNTP newsgroup(s).