RISC-V Fix for 6.4-rc7

* A documentation patch describing how we use patchwork.
 -----BEGIN PGP SIGNATURE-----
 
 iQJHBAABCAAxFiEEKzw3R0RoQ7JKlDp6LhMZ81+7GIkFAmSMgTQTHHBhbG1lckBk
 YWJiZWx0LmNvbQAKCRAuExnzX7sYiYzcD/9sB1vVr+4/NHDdVEAOKhXm4KO30Gup
 HM+HG7Mv/H0C7ogTGBqP7r3qdXvehDy8KrTHScm5uZznNoPXRIa7HrI1m6r770xp
 OeopKoW3wDGcGjKpyytOezuaMcWusQhM5EgZsoKaFjzUgl/BC7KytKkGZCU1RkdZ
 8EPjvZwwXqMO+56YAacP1T2e8+9aP4cr1/HnwyejNOGOeacs+W+B0PleF6r8E3bQ
 CRoJL7jygktuIwjOTNZeuED0eTZMMC362Al7vWG2bPBt90Pj9Js/MDqzuRg6BjBY
 s1A6ijpjWYBJtca3ACA5SQT8XQBczDcAiZ9aMllYsmYYLHe7SQfDAUq62VhOdVn6
 4IwldF5jFmmgPO030826jrWt7pk4wwWTkqARuq6En8pft50XK3rePZ7HBEAFR0x0
 9qoKl8XyIEVmX8pyKk8WmdFZSftaCNxg/PyzcSMASS1etC7hn45nuTULuh2uf1fr
 xCuzRjcPK145zEONVs5dwdCoJ6zLquLz/K5tLarbK7Khu5hHcKwz8SVRhGaT+PE2
 2pvV0mTgXwVz6C12refu5lJ7jDA01Ygf6on3M0K+nKxqsJ493G8w/9VL/ItKN/nM
 GC3oaGbtIeHG4u51oLrKrm0BnH0aGyx2j7OJnn6jQ0anVAKFh3Kz7BcO272NKQ9M
 Dn9RXMHI0eQreQ==
 =130G
 -----END PGP SIGNATURE-----

Merge tag 'riscv-for-linus-6.4-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux

Pull RISC-V fix from Palmer Dabbelt:

 - A documentation patch describing how we use patchwork

* tag 'riscv-for-linus-6.4-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
  Documentation: RISC-V: patch-acceptance: mention patchwork's role

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. 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