All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: 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:35:04 +0200	[thread overview]
Message-ID: <d85d50d4-3f52-4440-a57a-260d7943179e@gmail.com> (raw)
In-Reply-To: <CANiq72=kAdq4TsCPvMWBwdzngeOst8g2cGzkk1DxM2yW=V4emQ@mail.gmail.com>

On 30.07.24 6:00 PM, Miguel Ojeda 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>

Did you apply it on 6.11-rc1?
 
> However, to keep our build Clippy-clean, it requires a a patch like:
> 
>     https://lore.kernel.org/rust-for-linux/20240730155702.1110144-1-ojeda@kernel.org/
> 
> which should ideally be applied together.

I think that I ran clippy, maybe that changed between 6.10 and 6.11. 
> I hope that helps!
> 
> (Nit: please avoid top-posting, see https://subspace.kernel.org/etiquette.html)

Sorry, I'm still getting used to using the mailing list.

Cheers,
Christian

  parent reply	other threads:[~2024-07-30 16:35 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
2024-07-30 16:35     ` Christian Schrefl [this message]
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=d85d50d4-3f52-4440-a57a-260d7943179e@gmail.com \
    --to=chrisi.schrefl@gmail.com \
    --cc=Jamie.Cunliffe@arm.com \
    --cc=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.