u-boot.git/doc/develop/codingstyle.rst, branch v2026.07

doc: Move the b4 guide into sending_patches

2026-07-06T14:28:50Z

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 Reviewed-by: Mattijs Korpershoek Reviewed-by: Tom Rini

doc: .clang-format description

2026-05-01T08:33:08Z

We cannot use .clang-format without modification. For instance U-Boot has some for each macros that Linux does not have. Adjust the description. Reviewed-by: Mattijs Korpershoek Reviewed-by: Quentin Schulz Signed-off-by: Heinrich Schuchardt

doc: develop: process: Document using b4 and patchwork for custodians

2026-01-28T20:20:07Z

- 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: Update b4 external link

2026-01-28T20:20:07Z

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 Reviewed-by: Quentin Schulz

Merge branch 'next'

2025-10-06T19:20:24Z

Merge the outstanding changes from the 'next' branch to master.

doc: Update coding style to recommend b4 for patch submission

2025-10-03T03:59:34Z

Replace references to patman with b4 as the recommended tool for preparing and sending patches. b4 is widely adopted in the Linux kernel community and U-Boot ships with configuration to simplify its use with the project mailing list. The updated guidelines describe how to prepare series with b4, handle cover letters and recipient lists, run style checks, and send patches safely. Instructions also highlight how to collect and apply review tags before resending. This change documents the preferred workflow for contributors and ensures consistency with common practices across related upstream communities. Reviewed-by: Neil Armstrong Reviewed-by: Mattijs Korpershoek Signed-off-by: Javier Tia

doc: Update U-Boot coding style guide with clang-format usage

2025-09-16T19:45:00Z

The U-Boot coding style guide has been updated to include information about using the `.clang-format` configuration file for automatic code formatting. This ensures consistent formatting across the entire codebase and aligns with Linux kernel coding standards. The goal with introducing a predefined coding style is consistency rather than personal preference. The .clang-format file is copied directly from the Linux kernel without any modifications, ensuring complete compatibility with kernel coding standards. Include comprehensive best practices for using clang-format, specifically guidance on formatting only changed blocks versus entire files, creating separate formatting-only commits for better code review, and leveraging git clang-format for targeted formatting. Add examples of editor integrations. This enhancement will help maintainers and contributors to easily adhere to U-Boot coding standards. Signed-off-by: Javier Tia

doc/develop/codingstyle.rst: Expand to include CONFIG_IS_ENABLED and PHASE_

2025-04-11T18:16:44Z

Expand the conditional compilation section to explain when to use CONFIG_IS_ENABLED rather than IS_ENABLED and provide an example. Next, note what the PHASE_ macro is supposed to be used for as well. Signed-off-by: Tom Rini

doc/develop/codingstyle.rst: Add a section on conditional compilation

2025-04-11T18:16:44Z

In order to make a start on explaining how and when to use certain macros, we need to document their usage somewhere. As a first step, take section 21 of the v6.13 Linux Kernel coding-style document on conditional compilation, verbatim, and add it to our documentation. Further rewording to be clearer about U-Boot will be done next. Signed-off-by: Tom Rini

Restore patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet"

2024-05-20T19:35:03Z

As part of bringing the master branch back in to next, we need to allow for all of these changes to exist here. Reported-by: Jonas Karlman Signed-off-by: Tom Rini