From: Boqun Feng <boqun.feng@gmail.com>
To: rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Open Meeting at March 27
Date: Mon, 25 Mar 2024 11:23:15 -0700 [thread overview]
Message-ID: <ZgHBE8yRuZ5_8Bwi@boqun-archlinux> (raw)
In-Reply-To: <Za_9bJxeyW0pddKL@boqun-archlinux>
Hi all,
Another rc1 another meeting! Please join us:
https://meet.google.com/vii-meij-xpw
at 19:00 UTC Wednesday, March 27th.
I want to do a better job on the agenda, so with the help of folks, I
put together a list of highlight news below. And during the meeting we
can discuss:
* Your question first!
* The list for anything that anyone is interested.
Looking forwards to seeing you there!
Regards,
Boqun
---------------------------------------------------->8
What's the news since v6.8-rc1:
* v6.9 pull request:
https://lore.kernel.org/rust-for-linux/20240309133817.335439-1-ojeda@kernel.org/
* ARM64 support is merged via ARM64 PR:
https://lore.kernel.org/linux-arm-kernel/20240313160018.2603344-1-catalin.marinas@arm.com/
* First kselftest for Rust:
https://lore.kernel.org/lkml/fc9ccbf3-6b7d-46d3-a8da-54d5dc78a81c@linuxfoundation.org/
* Rust block device driver API RFC v2 is out:
https://lore.kernel.org/rust-for-linux/ZfdhyfLWBIFtKO81@casper.infradead.org/T/#t
* A few "topic branches" have been created/renamed to help collaboration:
https://rust-for-linux.com/branches#topic-branches
* Memory ordering model discussion:
https://github.com/Rust-for-Linux/linux/issues/1067
https://lore.kernel.org/rust-for-linux/20240322233838.868874-1-boqun.feng@gmail.com/
next prev parent reply other threads:[~2024-03-25 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 1:12 Rust for Linux Open Meeting Miguel Ojeda
2023-09-09 17:23 ` Boqun Feng
2023-11-06 18:52 ` No Open Meeting at Nov 15 Boqun Feng
2024-01-23 17:54 ` Open Meeting at Jan 24 Boqun Feng
2024-03-25 18:23 ` Boqun Feng [this message]
2024-05-28 15:58 ` Open Meeting at May 29 Boqun Feng
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=ZgHBE8yRuZ5_8Bwi@boqun-archlinux \
--to=boqun.feng@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 read-only IMAP folder(s) and NNTP newsgroup(s).