doc: Move the b4 guide into sending_patches

The b4 contributor guide sits in the coding-style document, which is an
odd place for it. Move it into sending_patches.rst, next to the patman
note, so both patch-sending tools are described together.

The b4_contrib label moves with it, so the reference from process.rst
still resolves.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
Reviewed-by: Tom Rini <trini@konsulko.com>

2 files changed, 51 insertions, 48 deletions

diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst
index 26881cf3900..b8d2bf23a54 100644
--- a/doc/develop/codingstyle.rst
+++ b/doc/develop/codingstyle.rst
@@ -24,54 +24,6 @@ The following rules apply:
   <https://peps.python.org/pep-0008/>`_. Use `pylint
   <https://github.com/pylint-dev/pylint>`_ for checking the code.
 
-.. _b4_contrib:
-
-* Use the `b4 <https://b4.docs.kernel.org/en/latest/>`__ tool to prepare and
-  send your patches. b4 has become the preferred tool to sending patches for many
-  Linux kernel contributors, and U-Boot ships with a ready-to-use ``.b4-config`` that
-  targets ``u-boot@lists.denx.de`` and integrates with ``scripts/get_maintainer.pl`` for
-  recipient discovery.
-
-  Start a topical series with ``b4 prep`` and keep the commits organised with
-  ``git rebase -i``. ``b4 prep --edit-cover`` opens an editor for the cover
-  letter, while ``b4 prep --auto-to-cc`` collects reviewers and maintainers from
-  both the configuration file and ``scripts/get_maintainer.pl``.
-
-  .. code-block:: bash
-
-     b4 prep -n mmc-fixes
-     git rebase -i origin/master
-     b4 prep --edit-cover
-     b4 prep --auto-to-cc
-
-  Run the style checks before sending. ``b4 prep --check`` wraps the existing
-  tooling so you see the output from ``scripts/checkpatch.pl`` alongside b4's
-  own validation. You can always invoke ``scripts/checkpatch.pl`` directly for
-  additional runs.
-
-  .. code-block:: bash
-
-     b4 prep --check
-
-  When the series is ready, use ``b4 send``. Begin with ``--dry-run`` to review
-  the generated emails and ``--reflect`` to copy yourself for records before
-  dispatching to ``u-boot@lists.denx.de``.
-
-  .. code-block:: bash
-
-     b4 send --dry-run
-     b4 send --reflect
-     b4 send
-
-  After reviews arrive, collect Acked-by/Tested-by tags with ``b4 trailers -u``
-  and fold them into your commits before resending the updated series.
-
-  .. code-block:: bash
-
-     b4 trailers -u
-     git rebase -i origin/master
-     b4 send
-
 * Run ``scripts/checkpatch.pl`` directly or via ``b4 prep --check`` so that all
   issues are resolved *before* posting on the mailing list. For more information,
   read :doc:`checkpatch`.
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst
index e29fa175727..85f3003074f 100644
--- a/doc/develop/sending_patches.rst
+++ b/doc/develop/sending_patches.rst
@@ -17,6 +17,57 @@ A good introduction how to prepare for submitting patches can be found in the
 LWN article `How to Get Your Change Into the Linux Kernel
 <http://lwn.net/Articles/139918/>`_ as the same rules apply to U-Boot, too.
 
+.. _b4_contrib:
+
+Using b4
+--------
+
+Use the `b4 <https://b4.docs.kernel.org/en/latest/>`__ tool to prepare and send
+your patches. b4 has become the preferred tool to sending patches for many Linux
+kernel contributors, and U-Boot ships with a ready-to-use ``.b4-config`` that
+targets ``u-boot@lists.denx.de`` and integrates with ``scripts/get_maintainer.pl``
+for recipient discovery.
+
+Start a topical series with ``b4 prep`` and keep the commits organised with
+``git rebase -i``. ``b4 prep --edit-cover`` opens an editor for the cover letter,
+while ``b4 prep --auto-to-cc`` collects reviewers and maintainers from both the
+configuration file and ``scripts/get_maintainer.pl``.
+
+.. code-block:: bash
+
+   b4 prep -n mmc-fixes
+   git rebase -i origin/master
+   b4 prep --edit-cover
+   b4 prep --auto-to-cc
+
+Run the style checks before sending. ``b4 prep --check`` wraps the existing
+tooling so you see the output from ``scripts/checkpatch.pl`` alongside b4's own
+validation. You can always invoke ``scripts/checkpatch.pl`` directly for
+additional runs.
+
+.. code-block:: bash
+
+   b4 prep --check
+
+When the series is ready, use ``b4 send``. Begin with ``--dry-run`` to review the
+generated emails and ``--reflect`` to copy yourself for records before
+dispatching to ``u-boot@lists.denx.de``.
+
+.. code-block:: bash
+
+   b4 send --dry-run
+   b4 send --reflect
+   b4 send
+
+After reviews arrive, collect Acked-by/Tested-by tags with ``b4 trailers -u`` and
+fold them into your commits before resending the updated series.
+
+.. code-block:: bash
+
+   b4 trailers -u
+   git rebase -i origin/master
+   b4 send
+
 Using patman
 ------------