From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B7CC1C4332F for ; Thu, 13 Oct 2022 11:40:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229543AbiJMLkH (ORCPT ); Thu, 13 Oct 2022 07:40:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58222 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229613AbiJMLkH (ORCPT ); Thu, 13 Oct 2022 07:40:07 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4FC1F26AC1; Thu, 13 Oct 2022 04:40:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1665661206; x=1697197206; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=qwBNvrTGhKx7haBmbfNDVoNRn8CE3KTouJoIXdepuVk=; b=uxALg9MfiogGkx1Jk0Jk08w4QKYCn/e5Q1OqtPQO+Gi2Nao2cGrcv0CL B9pm12p3d08zY1CK2rd4RAghRp4s0QaK5rbvN0hbGeGtoZbo1p2iVjsQd t8BhNsRWsQeqYVZWBIxCbpJZS8ystAe9wXvtXN9jbh5dS5+HTvBjjWN9y 4poyG/e1XHZhXtjstj/mSMc7zIC30o1LBz67Z5yDNnGZqJs9LoJjn4Pqa S4obbkeULGb+1ETyTYhJtmNmr11pndvytRROKVOnJEEy4cE6Z2fhFbpEQ No4mDhkLfd+y6Q//itk78lDJMVx0e1NHMbCfdE7QLYZ/xuqxmkBWSUrVX g==; X-IronPort-AV: E=Sophos;i="5.95,180,1661842800"; d="scan'208";a="178539448" Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa4.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 13 Oct 2022 04:40:05 -0700 Received: from chn-vm-ex03.mchp-main.com (10.10.85.151) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12; Thu, 13 Oct 2022 04:40:03 -0700 Received: from wendy (10.10.115.15) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12 via Frontend Transport; Thu, 13 Oct 2022 04:40:02 -0700 Date: Thu, 13 Oct 2022 12:39:39 +0100 From: Conor Dooley To: Palmer Dabbelt CC: Conor Dooley , Atish Patra , , Paul Walmsley , Palmer Dabbelt , , , , , Subject: Re: [PATCH 4/4] Documentation: RISC-V: patch-acceptance: s/implementor/implementer Message-ID: References: <20221013045619.18906-1-palmer@rivosinc.com> <20221013045619.18906-5-palmer@rivosinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20221013045619.18906-5-palmer@rivosinc.com> Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Wed, Oct 12, 2022 at 09:56:19PM -0700, Palmer Dabbelt wrote: > From: Palmer Dabbelt > > Implementor does appear to be a word, but it's not very common. > > Suggested-by: Conor Dooley The overlords would probably rather this email got the credit but doesn't really matter for S-b tags. Reviewed-by: Conor Dooley > Signed-off-by: Palmer Dabbelt > --- > Documentation/riscv/patch-acceptance.rst | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/riscv/patch-acceptance.rst b/Documentation/riscv/patch-acceptance.rst > index 9fed6b318b49..89c7d8abd4bb 100644 > --- a/Documentation/riscv/patch-acceptance.rst > +++ b/Documentation/riscv/patch-acceptance.rst > @@ -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 > @@ -38,5 +38,5 @@ RISC-V extensions, we'll only accept patches for extensions that either: > for which a timeline for availability has been made public. > > Hardware that does not meet its published timelines may have support > -removed. (Implementors, may, of course, maintain their own Linux kernel > +removed. (Implementers, may, of course, maintain their own Linux kernel > trees containing code for any custom extensions that they wish.) > -- > 2.38.0 >