diff options
| author | Tom Rini <[email protected]> | 2026-07-06 08:12:19 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2026-07-06 08:28:51 -0600 |
| commit | 18761722e67d6e3770ab296a04fe3d40022e76d2 (patch) | |
| tree | e544dae54d83d5d3524e527c435be0395efe3a17 /doc/develop/testing.rst | |
| parent | a25c9bd19215ddd95d7494ebf8d842c46fdf3ba8 (diff) | |
| parent | 91b94aff149d2c6efe3afa81adaf5edcc6119221 (diff) | |
Merge patch series "Remove patman from the U-Boot tree"
Simon Glass <[email protected]> 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/[email protected]
Diffstat (limited to 'doc/develop/testing.rst')
| -rw-r--r-- | doc/develop/testing.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/develop/testing.rst b/doc/develop/testing.rst index 3a2b496fa00..1d19b49e82c 100644 --- a/doc/develop/testing.rst +++ b/doc/develop/testing.rst @@ -22,7 +22,7 @@ the quick ones, type this:: make qcheck -It is also possible to run just the tests for tools (patman, binman, etc.). +It is also possible to run just the tests for tools (binman, buildman, etc.). Such tests are included with those tools, i.e. no actual U-Boot unit tests are run. Type this:: |
