| Message ID | 20221013045619.18906-4-palmer@rivosinc.com (mailing list archive) |
|---|---|
| State | Superseded |
| Delegated to: | Palmer Dabbelt |
| Headers | show |
| Series | Documentation: RISC-V: patch-acceptance changes | expand |
On Thu, Oct 13, 2022 at 10:26 AM Palmer Dabbelt <palmer@rivosinc.com> wrote: > > From: Palmer Dabbelt <palmer@rivosinc.com> > > The current patch acceptance policy requires that specifications are > approved by the RISC-V foundation, but we rely on external > specifications as well. This explicitly calls out the UEFI > specifications that we're starting to depend on. > > Reviewed-by: Conor Dooley <conor.dooley@microchip.com> > Reviewed-by: Atish Patra <atishp@rivosinc.com> > Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com> Looks good to me from a KVM RISC-V perspective. Reviewed-by: Anup Patel <anup@brainfault.org> Regards, Anup > --- > Documentation/riscv/patch-acceptance.rst | 8 +++++--- > 1 file changed, 5 insertions(+), 3 deletions(-) > > diff --git a/Documentation/riscv/patch-acceptance.rst b/Documentation/riscv/patch-acceptance.rst > index 0a6199233ede..9fed6b318b49 100644 > --- a/Documentation/riscv/patch-acceptance.rst > +++ b/Documentation/riscv/patch-acceptance.rst > @@ -20,9 +20,11 @@ Submit Checklist Addendum > ------------------------- > We'll only accept patches for new modules or extensions if the > specifications for those modules or extensions are listed as being > -"Frozen" or "Ratified" by the RISC-V Foundation. (Developers may, of > -course, maintain their own Linux kernel trees that contain code for > -any draft extensions that they wish.) > +unlikely to be incompatibly changed in the future. For > +specifications from the RISC-V foundation this means "Frozen" or > +"Ratified", for the UEFI forum specifications this means a published > +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 > their own custom extensions. These custom extensions aren't required > -- > 2.38.0 > > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/Documentation/riscv/patch-acceptance.rst b/Documentation/riscv/patch-acceptance.rst index 0a6199233ede..9fed6b318b49 100644 --- a/Documentation/riscv/patch-acceptance.rst +++ b/Documentation/riscv/patch-acceptance.rst @@ -20,9 +20,11 @@ Submit Checklist Addendum ------------------------- We'll only accept patches for new modules or extensions if the specifications for those modules or extensions are listed as being -"Frozen" or "Ratified" by the RISC-V Foundation. (Developers may, of -course, maintain their own Linux kernel trees that contain code for -any draft extensions that they wish.) +unlikely to be incompatibly changed in the future. For +specifications from the RISC-V foundation this means "Frozen" or +"Ratified", for the UEFI forum specifications this means a published +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 their own custom extensions. These custom extensions aren't required