[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <LHGWBNSEDaOsx4BbADR1pZYqPV0KKhVaJ1Qvwe9h4UPeERRAA4s1DTIsnFR5rpHBGa6uIG1tU_4hTBXgjAc5BNwNqo0Rg_kOx2W_y0EUy_I=@metaspace.dk>
Date: Tue, 09 Jul 2024 06:00:46 +0000
From: nmi <nmi@...aspace.dk>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Miguel Ojeda <ojeda@...nel.org>, rust-for-linux@...r.kernel.org, linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org, Andreas Hindborg <a.hindborg@...sung.com>, Adam Bratschi-Kaye <ark.email@...il.com>, Sami Tolvanen <samitolvanen@...gle.com>
Subject: Re: [PATCH] rust: add `module_params` macro
Hi Luis,
On Monday, July 8th, 2024 at 23:42, Luis Chamberlain <mcgrof@...nel.org> wrote:
> I'm starting to feel the same way about modules, but modules requires
> more work than the firmware loader. And since I also know Andreas has
> already a lot on his plate, I'm at a cross roads. My above request for
> the firmware loader made sense to the person working on the firmware
> loader changes, but who would help on the modules side of things? And
> does this request make sense to help scale?
>
> The rationale here is that a rust binding means commitment then also
> from fresh blood to help co-maintain review C / Rust for exising code
> when there is will / desire to collaborate from an existing C maintainer.
>
> I realize this may be a lot to ask, but I think this is one of the
> responsible ways to ask to scale here.
I am not sure I am the right person for the task, because as you say, I have a lot on my plate. But perhaps lets schedule a call so I can get a sense of the required effort.
Best regards,
Andreas
Powered by blists - more mailing lists