Rather than pointing at the source code for b4, point the the official documentation. Also, use an anonymous reference for the link, per rST best practices.
Signed-off-by: Tom Rini <[email protected]> --- doc/develop/codingstyle.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst index 013bfebf7e48..7304eea0056a 100644 --- a/doc/develop/codingstyle.rst +++ b/doc/develop/codingstyle.rst @@ -24,7 +24,7 @@ The following rules apply: <https://peps.python.org/pep-0008/>`_. Use `pylint <https://github.com/pylint-dev/pylint>`_ for checking the code. -* Use the `b4 <https://git.kernel.org/pub/scm/utils/b4/b4.git/>`_ tool to prepare and +* 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 ``[email protected]`` and integrates with ``scripts/get_maintainer.pl`` for -- 2.43.0
