Documentation: RISC-V: Allow patches for non-standard behavior
authorPalmer Dabbelt <palmer@rivosinc.com>
Wed, 7 Dec 2022 02:08:13 +0000 (18:08 -0800)
committerPalmer Dabbelt <palmer@rivosinc.com>
Tue, 13 Dec 2022 17:38:21 +0000 (09:38 -0800)
commit936100d4507f2e9f0be4621b0c698180d65e8264
tree40314c51af08a67812379b88bc4fda613820ca0d
parent37f0ab1477994a0d0dc3c1e0de030fae07d37965
Documentation: RISC-V: Allow patches for non-standard behavior

The patch acceptance policy forbids accepting support for non-standard
behavior.  This policy was written in order to both steer implementers
towards the standards and to avoid coupling the upstream kernel too
tightly to vendor-specific features.  Those were good goals, but in
practice the policy just isn't working: every RISC-V system we have
needs vendor-specific behavior in the kernel and we end up taking that
support which violates the policy.  That's confusing for contributors,
which is the main reason we have a written policy in the first place.

So let's just start taking code for vendor-defined behavior.

Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Anup Patel <anup@brainfault.org>
Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
Link: https://lore.kernel.org/all/alpine.DEB.2.21.999.2211181027590.4480@utopia.booyaka.com/
[Palmer: merge in Paul's suggestions]
Link: https://lore.kernel.org/r/20221207020815.16214-3-palmer@rivosinc.com
Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
Documentation/riscv/patch-acceptance.rst