From: Greg KH <gregkh@linuxfoundation.org>
To: nmi <nmi@metaspace.dk>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
rust-for-linux@vger.kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andreas Hindborg <a.hindborg@samsung.com>,
Adam Bratschi-Kaye <ark.email@gmail.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH] rust: add `module_params` macro
Date: Tue, 9 Jul 2024 10:27:09 +0200 [thread overview]
Message-ID: <2024070924-darkening-knee-bfef@gregkh> (raw)
In-Reply-To: <LHGWBNSEDaOsx4BbADR1pZYqPV0KKhVaJ1Qvwe9h4UPeERRAA4s1DTIsnFR5rpHBGa6uIG1tU_4hTBXgjAc5BNwNqo0Rg_kOx2W_y0EUy_I=@metaspace.dk>
On Tue, Jul 09, 2024 at 06:00:46AM +0000, nmi wrote:
> Hi Luis,
>
> On Monday, July 8th, 2024 at 23:42, Luis Chamberlain <mcgrof@kernel.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.
Kernel development is done through emails, not calls :)
If a submitter isn't willing to maintain the code they submit, then it
should be rejected as maintance is the most important part.
Sorry,
greg k-h
next prev parent reply other threads:[~2024-07-09 8:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:15 [PATCH] rust: add `module_params` macro Andreas Hindborg
2024-07-05 11:33 ` Andreas Hindborg
2024-07-08 21:42 ` Luis Chamberlain
2024-07-09 6:00 ` nmi
2024-07-09 8:27 ` Greg KH [this message]
2024-07-09 9:25 ` nmi
2024-07-09 10:08 ` Miguel Ojeda
2024-07-18 17:15 ` Luis Chamberlain
2024-07-24 17:04 ` Sami Tolvanen
[not found] ` <CGME20240819200056eucas1p1589eddef05f72d97836f1d5be889048b@eucas1p1.samsung.com>
2024-08-19 20:00 ` Daniel Gomez
2024-08-19 21:59 ` Luis Chamberlain
2024-07-29 17:16 ` Benno Lossin
2024-08-01 11:29 ` Andreas Hindborg
2024-08-01 12:25 ` Benno Lossin
2024-08-01 13:40 ` Andreas Hindborg
2024-08-01 14:21 ` Benno Lossin
2024-08-01 15:11 ` Andreas Hindborg
2024-08-01 19:28 ` Benno Lossin
2024-08-02 10:27 ` Andreas Hindborg
2024-08-02 17:11 ` Benno Lossin
2024-08-05 10:55 ` Andreas Hindborg
2024-08-06 8:09 ` Benno Lossin
2024-08-15 13:11 ` Andreas Hindborg
2024-08-15 19:33 ` Benno Lossin
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=2024070924-darkening-knee-bfef@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@samsung.com \
--cc=ark.email@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.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).