Content of the first PR/RFC

[ojeda]

The plan of what will go into the first PR/RFC. Each will likely be a separate commit/patch. Not everything is strictly required, but good to write down anyway.

• Kbuild
• Kconfig
• Bindings / krustlib / ...
• Testing story (e.g. selftests, unit testing, related Kconfig entries, etc.)
• Other required changes in infrastructure
• First example driver (QEMU/virtio)
• Second example driver (ARM/RaspberryPi)

So far discussed in the LPC hackroom with @nickdesaulniers @geofft @joshtriplett @alex @cuviper @arndb Patrick McLean et. al.

[alex]

What else do we think needs to be done before this is ready to send upstream?

[kloenk]

Vendor dir for building (at least documentation via the KBUILD_CARGOFLAGS).
See #17

[kloenk]

We should probably also document what env variables get passed to cargo. I'm thinking of things like CARGO_HOME and CARGO_LOG, as well as RUST_BACKTRACE for build.rs scripts

[kloenk]

Also coding style seems missing/not followed

[ojeda]

Added Testing to the list as @alex mentioned it the other day.