Unverified Commit a39c6365 authored by Palmer Dabbelt's avatar Palmer Dabbelt
Browse files

Documentation: RISC-V: patch-acceptance: s/implementor/implementer 



Implementor does appear to be a word, but it's not very common.

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


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

Documentation/riscv/patch-acceptance.rst

+2 −2
Original line number Diff line number Diff line
@@ -26,7 +26,7 @@ specifications from the RISC-V foundation this means "Frozen" or 
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

Additionally, the RISC-V specification allows implementers to create

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

to go through any review or ratification process by the RISC-V

Foundation.  To avoid the maintenance complexity and potential
@@ -37,5 +37,5 @@ RISC-V extensions, we'll only consider patches for extensions that either: 
- Have been implemented in hardware that is widely available, per standard

  Linux practice.



(Implementors, may, of course, maintain their own Linux kernel trees containing

(Implementers, may, of course, maintain their own Linux kernel trees containing

code for any custom extensions that they wish.)