From: Leandro Coutinho <lescoutinhovr@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: wedsonaf@google.com
Subject: Mentorship Session: Writing Linux Kernel Modules in Rust
Date: Sun, 24 Jul 2022 16:46:08 -0300 [thread overview]
Message-ID: <CAN6UTaywU8NfeNVi2ZDfwgjo3LCKiQRbD9PUWKsRp33Gxo+4gg@mail.gmail.com> (raw)
Hi,
I don't know if it was already shared here, but Wedson did a nice presentation
for the Linux Foundation:
Mentorship Session: Writing Linux Kernel Modules in Rust
https://www.linuxfoundation.org/webinars/writing-linux-kernel-modules-in-rust/
He uses Neovim with rust-analyzer.
It's nice that it provides code navigation, completion, pop-up
documentation, ... cool stuff
Here's a basic setup for those who wanna try:
https://gist.github.com/tivrfoa/e956f090ff549e9dd04c9ececd3912f1
And if you like to use VS Code, it's even simpler, just run:
1. make rust-analyzer
2. open VS Code from the project root folder (where rust-project.json
was created).
3. install rust-analyzer extension
I tested a small refactoring, changed a function name, and it renamed in
all files that use it.
reply other threads:[~2022-07-24 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAN6UTaywU8NfeNVi2ZDfwgjo3LCKiQRbD9PUWKsRp33Gxo+4gg@mail.gmail.com \
--to=lescoutinhovr@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@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).