[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221013045619.18906-2-palmer@rivosinc.com>
Date: Wed, 12 Oct 2022 21:56:16 -0700
From: Palmer Dabbelt <palmer@...osinc.com>
To: Conor Dooley <conor@...nel.org>, Atish Patra <atishp@...osinc.com>
Cc: corbet@....net, Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, aou@...s.berkeley.edu,
conor.dooley@...rochip.com, Atish Patra <atishp@...osinc.com>,
linux-doc@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux@...osinc.com,
Palmer Dabbelt <palmer@...osinc.com>
Subject: [PATCH 1/4] Documentation: RISC-V: Fix a typo in patch-acceptance
From: Palmer Dabbelt <palmer@...osinc.com>
I just stumbled on this when modifying the docs.
Signed-off-by: Palmer Dabbelt <palmer@...osinc.com>
---
Documentation/riscv/patch-acceptance.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/riscv/patch-acceptance.rst b/Documentation/riscv/patch-acceptance.rst
index dfe0ac5624fb..5da6f9b273d6 100644
--- a/Documentation/riscv/patch-acceptance.rst
+++ b/Documentation/riscv/patch-acceptance.rst
@@ -29,7 +29,7 @@ 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
performance impact of adding kernel code for implementor-specific
-RISC-V extensions, we'll only to accept patches for extensions that
+RISC-V extensions, we'll only accept patches for extensions that
have been officially frozen or ratified by the RISC-V Foundation.
(Implementors, may, of course, maintain their own Linux kernel trees
containing code for any custom extensions that they wish.)
--
2.38.0
Powered by blists - more mailing lists