Unverified Commit 68eabc72 authored by Palmer Dabbelt's avatar Palmer Dabbelt
Browse files

Documentation: RISC-V: Mention the UEFI Standards 



The current patch acceptance policy requires that specifications are
approved by the RISC-V foundation, but we rely on external
specifications as well.  This explicitly calls out the UEFI
specifications that we're starting to depend on.

Reviewed-by: default avatarConor Dooley <conor.dooley@microchip.com>
Reviewed-by: default avatarAtish Patra <atishp@rivosinc.com>
Reviewed-by: default avatarAnup Patel <anup@brainfault.org>
Link: https://lore.kernel.org/r/20221207020815.16214-4-palmer@rivosinc.com


Signed-off-by: default avatarPalmer Dabbelt <palmer@rivosinc.com>
parent 936100d4

Documentation/riscv/patch-acceptance.rst

+5 −3
Original line number Diff line number Diff line
@@ -20,9 +20,11 @@ Submit Checklist Addendum 
-------------------------

We'll only accept patches for new modules or extensions if the

specifications for those modules or extensions are listed as being

"Frozen" or "Ratified" by the RISC-V Foundation.  (Developers may, of

course, maintain their own Linux kernel trees that contain code for

any draft extensions that they wish.)

unlikely to be incompatibly changed in the future.  For

specifications from the RISC-V foundation this means "Frozen" or

"Ratified", for the UEFI forum specifications this means a published

ECR.  (Developers may, of course, maintain their own Linux kernel trees

that contain code for any draft extensions that they wish.)



Additionally, the RISC-V specification allows implementors to create

their own custom extensions.  These custom extensions aren't required