0001 .. SPDX-License-Identifier: GPL-2.0
0002
0003 arch/riscv maintenance guidelines for developers
0004 ================================================
0005
0006 Overview
0007 --------
0008 The RISC-V instruction set architecture is developed in the open:
0009 in-progress drafts are available for all to review and to experiment
0010 with implementations. New module or extension drafts can change
0011 during the development process - sometimes in ways that are
0012 incompatible with previous drafts. This flexibility can present a
0013 challenge for RISC-V Linux maintenance. Linux maintainers disapprove
0014 of churn, and the Linux development process prefers well-reviewed and
0015 tested code over experimental code. We wish to extend these same
0016 principles to the RISC-V-related code that will be accepted for
0017 inclusion in the kernel.
0018
0019 Submit Checklist Addendum
0020 -------------------------
0021 We'll only accept patches for new modules or extensions if the
0022 specifications for those modules or extensions are listed as being
0023 "Frozen" or "Ratified" by the RISC-V Foundation. (Developers may, of
0024 course, maintain their own Linux kernel trees that contain code for
0025 any draft extensions that they wish.)
0026
0027 Additionally, the RISC-V specification allows implementors to create
0028 their own custom extensions. These custom extensions aren't required
0029 to go through any review or ratification process by the RISC-V
0030 Foundation. To avoid the maintenance complexity and potential
0031 performance impact of adding kernel code for implementor-specific
0032 RISC-V extensions, we'll only to accept patches for extensions that
0033 have been officially frozen or ratified by the RISC-V Foundation.
0034 (Implementors, may, of course, maintain their own Linux kernel trees
0035 containing code for any custom extensions that they wish.)
