RISC-V development partners can use the following lists for patch discussion and review of patches.
All patches developed by dev-partners and all discussions for a particular patch should be sent to this lists.
The lists are used as an internal review tool before contributing patches upstream.
The main goal of these lists is to technical enable feedback and let others:
- Check if patches meet formal requirements (commit message, coding style, license)
- Check if patches meet functional requirements (does it do what it should do?)
- Check if patches are complete
- Check if patches meet RVI-internal policies (naming, style)
- Check the lifecycle state of the corresponding specification
Note, that the lists require a subscription before posting.
Also note, that the mail archives are public.
The existing lists and their archives are:
- Simulator related projects (qemu, etc.): firstname.lastname@example.org, archive
- OS kernel related projects (Linux, FreeBSD, etc.): email@example.com, archive
- GNU Toolchain related projects (Binutils, GCC, glibc, gdb, etc.): firstname.lastname@example.org, archive
- LLVM related projects (llvm, ldb, etc.): email@example.com, archive
- Libraries (OpenSSL, jemalloc, etc.): firstname.lastname@example.org, archive