From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [Ksummit-discuss] [TECH TOPIC] Rust
Date: Sat, 18 Jun 2022 23:42:07 +0300 [thread overview]
Message-ID: <Yq44nyu7P1uhBVGi@pendragon.ideasonboard.com> (raw)
Message-ID: <20220618204207.SOUP1SIWSRd_ExcNPaec34WaPRdMaumu4f67XCcF9Oc@z> (raw)
In-Reply-To: <CANiq72nNKvFqQs9Euy=_McfcHf0-dC_oPB3r8ZJii2L3sfVjaw@mail.gmail.com>
Hi Miguel,
On Sat, Jun 18, 2022 at 10:33:01PM +0200, Miguel Ojeda wrote:
> The effort to add Rust support to the kernel is ongoing. There has
> been progress in different areas during the last year, and there are
> several topics that could benefit from discussion:
>
> - Dividing the `kernel` crate into pieces, dependency management
> between internal crates, writing crates in the rest of the kernel
> tree, etc.
>
> - Whether to allow dependencies on external crates and vendoring of
> useful third-party crates.
>
> - Toolchain requirements in the future and status of Rust unstable features.
>
> - The future of GCC builds: upcoming compilers, their status and
> ETAs, adding the kernel as a testing case for them...
>
> - Steps needed for further integration in the different kernel CIs,
> running tests, etc.
>
> - Documentation setup on kernel.org and integration between
> Sphinx/kernel-doc and rustdoc (this can be part of the documentation
> tech topic submitted earlier by Jon).
>
> - Discussion with prospective maintainers that want to use Rust for
> their subsystem.
All previous topics but this one are technical. To restore the balance a
bit (and also because I believe it's important to the success of this
project :-)), I'd like to also discuss the impact on the kernel
maintenance at large, beyond just the maintainers who opt in to be early
adopters of rust in their subsystem.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-06-18 20:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 20:33 Miguel Ojeda
2022-06-18 20:42 ` Laurent Pinchart [this message]
2022-06-18 20:42 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:44 ` Laurent Pinchart
2022-06-18 20:44 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-18 20:49 ` Miguel Ojeda
2022-06-19 6:13 ` Christoph Hellwig
2022-06-19 6:13 ` [Ksummit-discuss] " Christoph Hellwig
2022-06-19 10:04 ` Laurent Pinchart
2022-06-19 10:04 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 12:56 ` James Bottomley
2022-06-19 12:56 ` [Ksummit-discuss] " James Bottomley
2022-06-19 13:19 ` Jens Axboe
2022-06-19 13:19 ` [Ksummit-discuss] " Jens Axboe
2022-06-19 13:53 ` Laurent Pinchart
2022-06-19 13:53 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 14:27 ` James Bottomley
2022-06-19 14:27 ` [Ksummit-discuss] " James Bottomley
2022-06-19 14:45 ` [MAINTAINER SUMMIT] Are we becoming too fearful? [was Re: [TECH TOPIC] Rust] James Bottomley
2022-06-19 14:45 ` [Ksummit-discuss] " James Bottomley
2022-06-22 9:59 ` Linus Walleij
2022-06-22 10:57 ` Laurent Pinchart
2022-06-22 12:01 ` Linus Walleij
2022-06-22 12:09 ` Laurent Pinchart
2022-06-22 23:13 ` NeilBrown
2022-06-23 11:37 ` James Bottomley
2022-06-25 12:03 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2022-06-25 11:45 ` [Ksummit-discuss] [TECH TOPIC] Rust Mauro Carvalho Chehab
2022-06-25 14:15 ` James Bottomley
2022-06-25 16:18 ` Mauro Carvalho Chehab
2022-06-25 22:29 ` Linus Walleij
2022-06-26 2:52 ` Theodore Ts'o
2022-06-26 3:18 ` Al Viro
2022-06-19 13:49 ` Laurent Pinchart
2022-06-19 13:49 ` [Ksummit-discuss] " Laurent Pinchart
2022-06-19 19:08 ` Geert Uytterhoeven
2022-06-19 19:08 ` [Ksummit-discuss] " Geert Uytterhoeven
2022-06-19 20:57 ` Matthew Wilcox
2022-06-20 13:53 ` Linus Walleij
2022-06-20 14:08 ` James Bottomley
2022-06-21 15:11 ` Dan Carpenter
2022-06-23 10:58 ` [TECH TOPIC] Why is devm_kzalloc() harmful and what can we do about it Laurent Pinchart
2022-06-23 11:24 ` Dan Carpenter
2022-06-23 11:31 ` Laurent Pinchart
2022-06-21 9:49 ` [TECH TOPIC] Rust David Woodhouse
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=Yq44nyu7P1uhBVGi@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.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