From: Robin Randhawa <robin.randhawa@arm.com>
To: rust-for-linux@vger.kernel.org
Cc: nd@arm.com
Subject: Meeting minutes (Sat 8 May 2021)
Date: Sat, 8 May 2021 21:22:58 +0100 [thread overview]
Message-ID: <20210508202258.m7uk6cfxzyghzu7f@FVFF77RQQ05N> (raw)
Hi folks.
Summarised meeting minutes (Saturday 8th May 2021)
--------------------------------------------------
News
----
* "Good-first-issue" tag added to current issues. We got a contributor as a
result!
* A question came up: What fields do we need in the module macro ? Some mods
made to the macro as a result.
* Rustdoc feature that is used by the project is now stabilised in Rust. Also
@argfile.
* RISC-V support added to CI.
* Thanks to Finn and others, we can now use rust-analyzer for all the crates
used by the kernel and dependencies.
* Improved nixOS support.
* Driver contribution: Dummy network driver, contributed by Finn.
* Driver contribution: RNG driver for use on RPi, contributed by Sven.
General comments
----------------
* As discussed previously, there shall now be 2 meetings moving forwards. One
every alternate Saturday and another one during the working week.
The former is for a free form, informal, general catch-up. The latter is a
technically focused one.
Apart from these 2 meetings, if anyone has any pressing matters to discuss,
please send an email out to the list and folks can decide if they want to meet
to discuss.
For all meets, please try and share an agenda ahead of time so folks can prep
accordingly.
* Generally speaking, PRs should be the way to go for any code that needs
discussing.
* When using qemu note that most distros as of now do not have a sufficiently
new one. Eg Working with RISC-V will need qemu v6.
Questions and Answers
---------------------
Q Should wrapper structs use repr(transparent) ?
- No
Q Should everything that wraps a pointer implement the PointerWrapper Trait ?
- If there is an intent to pass a pointer from Rust -> C and then back, that’s
where the trait is used.
- There is a DenyList feature in bindgen that can be used to deal with
problematic structs. Also OpaqueList.
Q Can we not use cargo ? It would help with dependency management etc.
- No. Reasons enumerated here: https://github.com/Rust-for-Linux/linux/pull/52.
Cargo has a bunch of problems that need resolving (output interleaving with
Makefiles, cargo workspace issues).
Q Why are we using Cstrings that are different from the std lib ?
- Because they need to be null terminated. Alternative strategies that guarantee
null termination welcome.
Q What about the previously discussed use of the Zulip chat platform ?
- Not done yet. Should happen shortly. ** Action: Miguel **
Cheers,
Robin
next reply other threads:[~2021-05-08 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 20:22 Robin Randhawa [this message]
2021-05-08 20:59 ` Meeting minutes (Sat 8 May 2021) Miguel Ojeda
2021-05-08 23:13 ` Leandro Coutinho
2021-05-10 16:56 ` Wei Liu
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=20210508202258.m7uk6cfxzyghzu7f@FVFF77RQQ05N \
--to=robin.randhawa@arm.com \
--cc=nd@arm.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).