diff options
author | Palmer Dabbelt <[email protected]> | 2022-12-06 18:08:13 -0800 |
---|---|---|
committer | Palmer Dabbelt <[email protected]> | 2022-12-13 09:38:21 -0800 |
commit | 936100d4507f2e9f0be4621b0c698180d65e8264 (patch) | |
tree | 40314c51af08a67812379b88bc4fda613820ca0d /lib/mpi/mpi-sub-ui.c | |
parent | 37f0ab1477994a0d0dc3c1e0de030fae07d37965 (diff) |
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 <[email protected]>
Reviewed-by: Anup Patel <[email protected]>
Signed-off-by: Paul Walmsley <[email protected]>
Link: https://lore.kernel.org/all/[email protected]/
[Palmer: merge in Paul's suggestions]
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Palmer Dabbelt <[email protected]>
Diffstat (limited to 'lib/mpi/mpi-sub-ui.c')
0 files changed, 0 insertions, 0 deletions