From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, Miguel Ojeda <ojeda@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
rust-for-linux@vger.kernel.org,
Jamie Cunliffe <Jamie.Cunliffe@arm.com>,
Sven Van Asbroeck <thesven73@gmail.com>
Subject: Re: [PATCH 1/1] arm: rust: Enable Rust support for ARMv7
Date: Mon, 10 Jun 2024 21:37:04 +0200 [thread overview]
Message-ID: <f798777d-6a56-45d4-8136-6aa9e0e77abc@gmail.com> (raw)
In-Reply-To: <5a8a6b44-9f89-4e26-869c-e9361da4cb5c@lunn.ch>
On 10.06.24 9:00 PM, Andrew Lunn wrote:
>> --- a/Documentation/rust/arch-support.rst
>> +++ b/Documentation/rust/arch-support.rst
>> @@ -15,6 +15,7 @@ support corresponds to ``S`` values in the ``MAINTAINERS`` file.
>> ============= ================ ==============================================
>> Architecture Level of support Constraints
>> ============= ================ ==============================================
>> +``arm`` Maintained ARMv7 Little Endian only.
>
> Might be a FAQ, but what does Maintained mean here? Should you be
> adding yourself to the RUST entry in MAINTAINERS? You are Maintaining
> Rust on ARMv7 and so should be given credit/responsibility for that in
> MAINTAINERS?
From my side I can/will take a look if there are issues/patches related to this, but I
can't be sure how fast I'll be able to respond and I don't feel qualified to handle
larger or more complicated issues myself.
But there isn't a MAINTAINERS entry depending on the architecture, so I'm not sure
who will be responsible for this.
Miguel how is the support handled for the other architectures?
next prev parent reply other threads:[~2024-06-10 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 22:30 [PATCH 1/1] arm: rust: Enable Rust support for ARMv7 Christian Schrefl
2024-06-08 12:16 ` Miguel Ojeda
2024-06-08 13:57 ` Christian Schrefl
2024-06-08 12:42 ` Geert Stappers
2024-06-10 19:00 ` Andrew Lunn
2024-06-10 19:37 ` Christian Schrefl [this message]
2024-06-10 21:19 ` 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=f798777d-6a56-45d4-8136-6aa9e0e77abc@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=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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).