public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH 1/3] Documentation: RISC-V: Fix a typo in patch-acceptance
Date: Tue, 20 Sep 2022 17:56:59 +0100	[thread overview]
Message-ID: <Yynw26jVIvHSSQ+6@spud> (raw)
In-Reply-To: <20220920140138.27210-1-palmer@rivosinc.com>

On Tue, Sep 20, 2022 at 07:01:37AM -0700, Palmer Dabbelt wrote:
> I just stumbled on this when modifying the docs.
> 
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.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

s/implementor/implementer no? Or is this an American spelling?

> -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.34.1
> 
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2022-09-20 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20 14:01 [PATCH 1/3] Documentation: RISC-V: Fix a typo in patch-acceptance Palmer Dabbelt
2022-09-20 14:01 ` [PATCH 2/3] Documentation: RISC-V: Allow patches for non-standard behavior Palmer Dabbelt
2022-09-20 17:19   ` Conor Dooley
2022-10-13  4:56     ` Palmer Dabbelt
2022-09-20 14:01 ` [PATCH 3/3] Documentation: RISC-V: Mention the UEFI Standards Palmer Dabbelt
2022-09-20 17:49   ` Conor Dooley
2022-10-13  4:56     ` Palmer Dabbelt
2022-09-26 17:34   ` Atish Patra
2022-10-13  4:56     ` Palmer Dabbelt
2022-09-20 16:56 ` Conor Dooley [this message]
2022-10-13  4:56   ` [PATCH 1/3] Documentation: RISC-V: Fix a typo in patch-acceptance Palmer Dabbelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yynw26jVIvHSSQ+6@spud \
    --to=conor@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@rivosinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox