u-boot/u-boot.git, branch master

Prepare v2026.07

2026-07-06T23:50:43+00:00

Signed-off-by: Tom Rini

Merge patch series "Remove patman from the U-Boot tree"

2026-07-06T14:28:51+00:00

Simon Glass says: patman is now maintained as a standalone 'patch-manager' package, so remove it from the tree. The command becomes a stub that tells people to run 'pip install patch-manager'. buildman still imports the shared modules commit and patchstream (along with their dependencies), so this series leaves those in place. It drops the tool's code, tests, CI hooks and packaging, and removes the in-tree documentation, moving the b4 contributor guide alongside the patman note in the patch-sending docs. It also adds a .patman-defaults file so the external tool is set up for U-Boot, next to the existing .b4-config. Where the CI jobs relied on patman's requirements for the setuptools that pylibfdt needs, they now install scripts/dtc/pylibfdt/requirements.txt instead. More could be done here: commit and patchstream (and their dependencies series, get_maintainer and settings) only remain because buildman still imports them. A follow-up could move those into u_boot_pylib (or buildman itself) and drop the rest, leaving tools/patman as just the stub. Link: https://lore.kernel.org/r/20260705193251.2190705-1-sjg@chromium.org

patman: Remove the patch-management code

2026-07-06T14:28:51+00:00

Delete the command-line tool and its supporting modules, now that this functionality lives in the standalone patch-manager package. Keep the modules that buildman still imports (commit and patchstream, plus their dependencies series, get_maintainer and settings), along with the stub command. Trim __init__.py to match. Signed-off-by: Simon Glass

patman: Remove the test suite

2026-07-06T14:28:51+00:00

These tests cover the patch-management functionality, which is being removed from the tree in favour of the standalone patch-manager package. Drop the tests and their data files. Signed-off-by: Simon Glass

patman: Replace the tool with a stub for patch-manager

2026-07-06T14:28:51+00:00

patman is now maintained as a standalone 'patch-manager' package, rather than in the U-Boot tree. Replace the command with a small stub which tells people how to install it. buildman still uses the shared modules commit and patchstream (and their dependencies), so leave those in place; the patches that follow remove the patch-management code itself. Signed-off-by: Simon Glass

patman: Add a .patman-defaults file for U-Boot

2026-07-06T14:28:51+00:00

patman is now installed from the separate patch-manager package. It reads a .patman-defaults file from the tree root as its lowest-priority config, so a project can ship defaults that developers still override from their own ~/.patman, a local .patman or the command line. This behaviour is new in patman version 0.0.20 Add one for U-Boot, alongside .b4-config, pinning the patchwork server and the get_maintainer.pl invocation so the tool works out of the box without depending on patman's built-in defaults. A few other settings are listed, commented out, as a starting point. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

test: Stop running the patman tests

2026-07-06T14:28:51+00:00

The patman tests no longer exist in the tree, so drop them from the test/run script (used by 'make tcheck' and friends) and from the tools-testing example in the documentation. Signed-off-by: Simon Glass

tools: Stop packaging patman as a pip module

2026-07-06T14:28:50+00:00

patman is no longer shipped from the U-Boot tree, so drop it from the 'make pip' target and from make_pip.sh, and remove its packaging files (setup.py, pyproject.toml, requirements.txt). Nothing else refers to them by this point in the series, so they can go. Also fix binman's pyproject.toml, which declares package-data for a 'patman' package (a copy-paste leftover); use 'binman' instead. Signed-off-by: Simon Glass

tools: docker: Drop patman from the CI image

2026-07-06T14:28:50+00:00

The CI runner image pre-caches pip packages by downloading each tool's requirements.txt from master. A later patch removes patman's requirements.txt from the tree, so stop fetching and installing it. The same step already installs setuptools explicitly (patman's requirements list it too), so this needs nothing further. This takes effect the next time someone rebuilds the image; the existing image keeps working in the meantime. Signed-off-by: Simon Glass

CI: Stop building and testing patman

2026-07-06T14:28:50+00:00

patman is now just a stub, so drop its requirements file and its 'patman test' run from the Azure and GitLab pipelines. Signed-off-by: Simon Glass Reviewed-by: Tom Rini