[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240905-documentation-b4-advert-v2-1-24d686ba4117@kernel.org>
Date: Thu, 05 Sep 2024 13:33:33 +0100
From: Mark Brown <broonie@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
workflows@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Shuah Khan <skhan@...uxfoundation.org>,
Mark Brown <broonie@...nel.org>
Subject: [PATCH v2] docs: submitting-patches: Advertise b4
b4 is now widely used and is quite helpful for a lot of the things that
submitting-patches covers, let's advertise it to submitters to try to make
their lives easier and reduce the number of procedural issues maintainers
see.
Reviewed-by: Shuah Khan <skhan@...uxfoundation.org>
Signed-off-by: Mark Brown <broonie@...nel.org>
---
Changes in v2:
- Remove some blank lines.
- Link to v1: https://lore.kernel.org/r/20240903-documentation-b4-advert-v1-1-c89d6f5db7b1@kernel.org
---
Documentation/process/submitting-patches.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index f310f2f36666..1518bd57adab 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -842,6 +842,14 @@ Make sure that base commit is in an official maintainer/mainline tree
and not in some internal, accessible only to you tree - otherwise it
would be worthless.
+Tooling
+-------
+
+Many of the technical aspects of this process can be automated using
+b4, documented at <https://b4.docs.kernel.org/en/latest/>. This can
+help with things like tracking dependencies, running checkpatch and
+with formatting and sending mails.
+
References
----------
---
base-commit: 7c626ce4bae1ac14f60076d00eafe71af30450ba
change-id: 20240903-documentation-b4-advert-18016e83d7d9
Best regards,
--
Mark Brown <broonie@...nel.org>
Powered by blists - more mailing lists