Documentation: RISC-V: patch-acceptance: mention patchwork's role
Subsystems (2)
PATCH v2 1/1 Documentation: RISC-V: patch-acceptance: mention patchwork's role
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.
---
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 ¯\_(ツ)_/¯
Changes in v2:
- mention that riscv/master is now also a possible application target.
--- Documentation/riscv/patch-acceptance.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
Documentation/riscv/patch-acceptance.rst +18 -0
@@ -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. Failing those, it will use the RISC-V `master` branch. +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
Signature · 7 lines
2.39.2 _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 5 lines · Conor Dooley
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.
Quoted 7 lines
Add a short note to the patch-acceptance document to that end.
Signed-off-by Conor Dooley <[email protected]>---
I was also not sure if this was the correct doc for this, or whether aprocess/maintainer-riscv.rstfile was better suited. There's clearly no rush on this though so ¯\_(ツ)_/¯
I'm fine with this file. Thanks for adding it!
This patch was applied to riscv/linux.git (fixes) by Palmer Dabbelt <[email protected]>:
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <[email protected]>:
Quoted 8 lines · On Tue, 6 Jun 2023 07:59:19 +0100 you wrote:
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.
[...]
Here is the summary with links:
- [v2] Documentation: RISC-V: patch-acceptance: mention patchwork's role
https://git.kernel.org/riscv/c/b104dbedbe61
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Palmer Dabbelt
AppliedQuoted 8 lines · Conor Dooley
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.
[...]
Applied, thanks!
[1/1] Documentation: RISC-V: patch-acceptance: mention patchwork's role
https://git.kernel.org/palmer/c/b104dbedbe61
Best regards,
Signature · 1 line
Palmer Dabbelt <[email protected]>