Palmer suggested at some point, not sure if it was in one of the weekly linux-riscv syncs, or a conversation at FOSDEM, that we should document the role of the automation running on our patchwork instance plays in patch acceptance. Add a short note to the patch-acceptance document to that end. Signed-off-by: Conor Dooley <conor.dooley@xxxxxxxxxxxxx> --- The bit about fixes being applied to riscv/fixes is not actually correct, it's actually linux-next/pending-fixes. We've not had issues with the fixes branch being broken in a while, but I switched it over to pending-fixes due to the KVM breakage. I'll swap back to match the documentation I'm adding. I was also not sure if this was the correct doc for this, or whether a process/maintainer-riscv.rst file was better suited. There's clearly no rush on this though so ¯\_(ツ)_/¯ CC: Björn Töpel <bjorn@xxxxxxxxxx> CC: Palmer Dabbelt <palmer@xxxxxxxxxxx> CC: Paul Walmsley <paul.walmsley@xxxxxxxxxx> CC: Jonathan Corbet <corbet@xxxxxxx> CC: linux-riscv@xxxxxxxxxxxxxxxxxxx CC: linux-doc@xxxxxxxxxxxxxxx --- Documentation/riscv/patch-acceptance.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/Documentation/riscv/patch-acceptance.rst b/Documentation/riscv/patch-acceptance.rst index 1d1fb885326b..76ec57626043 100644 --- a/Documentation/riscv/patch-acceptance.rst +++ b/Documentation/riscv/patch-acceptance.rst @@ -16,6 +16,24 @@ tested code over experimental code. We wish to extend these same principles to the RISC-V-related code that will be accepted for inclusion in the kernel. +Patchwork +--------- + +RISC-V has a patchwork instance, where the status of patches can be checked: + + https://patchwork.kernel.org/project/linux-riscv/list/ + +If your patch does not appear in the default view, the RISC-V maintainers have +likely either requested changes, or expect it to be applied to another tree. + +Automation runs against this patchwork instance, building/testing patches as +they arrive. The automation applies patches against the current HEAD of the +RISC-V `for-next` and `fixes` branches, depending on whether the patch has been +detected as a fix. The exact commit to which a series has been applied will be +noted on patchwork. +Patches for which any of the checks fail are unlikely to be applied and in most +cases will need to be resubmitted. + Submit Checklist Addendum ------------------------- We'll only accept patches for new modules or extensions if the -- 2.39.2
