renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-16 17:23:55 +08:00
Code

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

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

Suggested-by: Conor Dooley <conor@kernel.org>
Reviewed-by: Anup Patel <anup@brainfault.org>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Link: https://lore.kernel.org/r/20221207020815.16214-5-palmer@rivosinc.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
This commit is contained in:
Palmer Dabbelt 2022-12-06 18:08:15 -08:00
parent 68eabc7202
commit a39c636506
No known key found for this signature in database
GPG Key ID: 2E1319F35FBB1889
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/riscv/patch-acceptance.rst
View File

@ -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.)