rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaviraj Kanagaraj <kavirajkanagaraj@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: [Rust for Linux] Call Sunday 2021-03-28 18:00 UTC
Date: Sun, 28 Mar 2021 22:42:28 +0200	[thread overview]
Message-ID: <27CFDC30-F1B9-4632-9F77-F1CFD1DE2508@gmail.com> (raw)
In-Reply-To: <CANiq72nd6eLtx4N9GbHR_sGOHJ1H=czPyza=Gctc=HU68aQ+qA@mail.gmail.com>

Hi Miguel!

No problems :) We can do introductions next time :)
It was really nice meeting you all :)

Thanks
Kaviraj 

Sent from my iPhone

> On 28-Mar-2021, at 22:20, Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> 
> Hi all,
> 
> Thanks all for joining!
> 
> Kaviraj: my apologies -- when someone new joins we do a round of
> introductions at the beginning of the meeting, but this time we did it
> at the end (but you had already left). If you join next meeting, I
> will make sure we do the introductions first! :-)
> 
> Updated schedule:
> 
>  - We are still targeting the 5th for the RFC. We can delay a week if
> we feel it is needed.
> 
>  - We will be adding a few things to the RFC:
>    + Some of the PRs in the queue.
>    + ppc64le support.
>    + Binder & a couple rust/kernel/ pieces for it.
>      * This does not necessarily mean Binder will go in the merge
> window -- it is more to show in the RFC how an actual working module
> looks like.
>    + Move/split of "Rust example".
>    + Kernel docs to be uploaded.
>    + Unstable feature list to be updated.
> 
> Other topics & news discussed:
> 
>  - Wedson joined as a maintainer!
> 
>  - RFC:
>    + The patches' split (preparation, Rust support, Binder).
>    + Attribution, git-blame, kernel process, etc.
> 
>  - `alloc`:
>    + We will likely end up with our own equivalent in the kernel, but
> this is medium-term. For the RFC and likely for the merge, we go with
> `alloc`.
>    + Ideally, this work could inform the Rust allocator WG!
> 
>  - Locking: enforcing correct order/patterns (or at least disallowing
> known-incorrect ones) via the type system or extra annotations.
> 
> Cheers,
> Miguel

  reply	other threads:[~2021-03-28 20:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 15:14 [Rust for Linux] Poll for call Miguel Ojeda
2021-03-16 16:57 ` Alex Gaynor
2021-03-18 20:58   ` Geert Stappers
2021-03-24 12:41 ` Miguel Ojeda
2021-03-24 21:12   ` [Rust for Linux] Call Sunday 2021-03-28 18:00 UTC Geert Stappers
2021-03-25  8:16     ` Miguel Ojeda
2021-03-25  9:02       ` Kaviraj Kanagaraj
2021-03-25  9:25         ` Miguel Ojeda
2021-03-27 11:49           ` Geert Stappers
2021-03-28 13:23             ` Miguel Ojeda
2021-03-28 20:20               ` Miguel Ojeda
2021-03-28 20:42                 ` Kaviraj Kanagaraj [this message]
2021-03-27 15:27       ` Joshua Abraham

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=27CFDC30-F1B9-4632-9F77-F1CFD1DE2508@gmail.com \
    --to=kavirajkanagaraj@gmail.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    /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).