[PATCH 0/2] docs: Adopt b4 as default patch submission workflow

[Javier Tia]

This small series updates U-Boot's contributor guidelines and
configuration to sync with current best practices around Linux kernel
patch submission.

The first patch updates doc/develop/codingstyle.rst to recommend the b4
tool instead of patman as the standard workflow for preparing and
sending patches. The revised documentation explains how to create and
manage series, run style checks, handle cover letters, discover mailing
list recipients, and collect review tags. This reflects widespread
adoption of b4 in the Linux kernel community and ensures U-Boot
contributors follow consistent, upstream-friendly practices.

The second patch simplifies the project’s .b4-config by removing custom
overrides for maintainer discovery. The upstream defaults in b4 already
invoke scripts/get_maintainer.pl with appropriate arguments, making the
redundant configuration unnecessary and reducing long-term maintenance.

These updates should make contributing smoother for new developers,
reduce duplication with upstream tooling, and ensure our workflow
evolves alongside improvements in b4.

Both patches were tested by preparing and sending patch series using the
updated configuration, confirming that maintainers and reviewers were
collected correctly and the emails were generated as expected.

Signed-off-by: Javier Tia <javier.tia at linaro.org>
---
Javier Tia (2):
      doc: Update coding style to recommend b4 for patch submission
      b4-config: Simplify configuration by relying on default b4 maintainer

 .b4-config                  |  6 ++---
 doc/develop/codingstyle.rst | 54 ++++++++++++++++++++++++++++++++++++++++-----
 2 files changed, 51 insertions(+), 9 deletions(-)
---
base-commit: 26efc940c865a04d345ac9d39f71746fc2821da6
change-id: 20250929-b4-docs-60da5560f06a

Best regards,
-- 
Javier Tia <javier.tia at linaro.org>