public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Asahi Lina <lina@asahilina.net>, Boqun Feng <boqun.feng@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Wedson Almeida Filho" <wedsonaf@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"John Stultz" <jstultz@google.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
	asahi@lists.linux.dev
Subject: Re: [PATCH] rust: time: New module for timekeeping functions
Date: Wed, 22 Feb 2023 09:33:03 +0100	[thread overview]
Message-ID: <87lekqm75s.ffs@tglx> (raw)
In-Reply-To: <98de1e48-085b-6edb-f1cc-2bf85180196f@asahilina.net>

Lina !

On Wed, Feb 22 2023 at 13:56, Asahi Lina wrote:
> On 22/02/2023 04.00, Thomas Gleixner wrote:
>> Be aware that my Rust foo is not even rusty it's close to non-existant.
>> That's probaly true for many maintainers you need to interact with.
>
> Please do feel free to reach out and ask any questions about all this
> crazy Rust stuff stuff! We're here to help and I know this is all new to
> a lot of maintainers. I want people to be comfortable that we aren't
> just creating more maintenance burden for everyone else.

I can only speak for myself. I'm comfortable and sufficiently curious
about this particular flavour of crazy.

I don't think these abstractions are a huge burden as long as the folks
who implement them talk to the relevant maintainers so we don't end
up with Rust inflicted burdens or ill defined abstractions.

> That's also another conversation that we probably need to have, how do
> we handle maintainership of Rust abstractions? I think Miguel mentioned
> that ideally existing subsystem maintainers take over their bits of the
> Rust side too over time, but of course a lot of people aren't going to
> be comfortable with that if they don't have a lot of Rust experience
> yet... personally I'm happy to sign up as co-maintainer or supporter of
> the abstractions I contribute, or maybe we can just pool resources and
> have people interested in Rust agree to help support this stuff for
> every subsystem?

Having subsystem maintainer teams supplemented with a Rust wizard, is
probably the best option at the moment. Time will tell as always.

Thanks,

        tglx



  reply	other threads:[~2023-02-22  8:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21  7:06 [PATCH] rust: time: New module for timekeeping functions Asahi Lina
2023-02-21  7:25 ` Eric Curtin
2023-02-21 11:23 ` Björn Roy Baron
2023-02-21 12:32 ` Thomas Gleixner
2023-02-21 14:06   ` Boqun Feng
2023-02-21 16:02     ` Thomas Gleixner
2023-02-21 16:31       ` Asahi Lina
2023-02-21 18:45         ` Thomas Gleixner
2023-02-21 21:33           ` Heghedus Razvan
2023-02-22  0:01             ` Thomas Gleixner
2023-02-22 19:55             ` Gary Guo
2023-02-21 22:29           ` Miguel Ojeda
2023-02-22  0:24             ` Thomas Gleixner
2023-02-22  2:54               ` Boqun Feng
2023-02-22  4:45                 ` Asahi Lina
2023-02-22  5:20                   ` Boqun Feng
2023-02-22  6:52                   ` Heghedus Razvan
2023-02-22 12:29                   ` Miguel Ojeda
2023-02-22 12:28               ` Miguel Ojeda
2023-02-21 16:27     ` Asahi Lina
2023-02-21 16:37       ` Asahi Lina
2023-02-21 19:00       ` Thomas Gleixner
2023-02-21 19:49         ` Boqun Feng
2023-02-22  4:56         ` Asahi Lina
2023-02-22  8:33           ` Thomas Gleixner [this message]
2023-02-21 17:13   ` Josh Stone
2023-02-21 21:46     ` Thomas Gleixner
2023-02-22  9:43       ` Gaelan Steele

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=87lekqm75s.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=alex.gaynor@gmail.com \
    --cc=asahi@lists.linux.dev \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=jstultz@google.com \
    --cc=lina@asahilina.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=wedsonaf@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