From 302c054d64a19c5bb579c3a74cc809f7338cf9de Mon Sep 17 00:00:00 2001 From: Tom Rini Date: Tue, 20 Jan 2026 16:31:46 -0600 Subject: doc: develop: process: Document using b4 and patchwork for custodians - We already have good custodian documentation for patchwork, add a reference and then link to it here. - Add a reference to the existing b4 documentation, and reference it here. - Note and link to patchwork integration, am/shazam and ty features of b4 as these are the most likely useful portions. Be specific about keeping the default ${summary} as that includes important information. Signed-off-by: Tom Rini Reviewed-by: Mattijs Korpershoek Reviewed-by: Quentin Schulz --- doc/develop/codingstyle.rst | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc/develop/codingstyle.rst') diff --git a/doc/develop/codingstyle.rst b/doc/develop/codingstyle.rst index 7304eea0056..2a69162fa95 100644 --- a/doc/develop/codingstyle.rst +++ b/doc/develop/codingstyle.rst @@ -24,6 +24,8 @@ The following rules apply: `_. Use `pylint `_ for checking the code. +.. _b4_contrib: + * Use the `b4 `__ 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 -- cgit v1.2.3