Skip to content

pw_poller: add ban_file support - #131

Merged
matttbe merged 2 commits into
linux-netdev:mainfrom
matttbe:poller-ban
Nov 6, 2026
Merged

matttbe merged 2 commits into
linux-netdev:mainfrom
matttbe:poller-ban

Conversation

@matttbe

@matttbe matttbe commented Nov 6, 2026

Copy link
Copy Markdown
Member

Add an optional [tests] ban_file config entry pointing to a file with lines of <user ID> <YYYY-MM-DD>.

The file is re-read for each series: if the submitter is banned until a future date, report user is currently banned instead of applying the patches.

The check is skipped when a tree is forced.

Add an optional [tests] ban_file config entry pointing to a file with
lines of "<user ID> <YYYY-MM-DD>". The file is re-read for each series;
if the submitter is banned until a future date, report "user is
currently banned" instead of applying the patches.

The check is skipped when a tree is forced.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
Add a docstring at the top of the file, similar to the one in
pw_brancher.py, listing all the config sections and options read by the
poller (including the ones handled by the Patchwork, lifetime and tester
helpers), with an example.

Signed-off-by: Matthieu Baerts <matttbe@kernel.org>
@matttbe

matttbe commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Deploying that as requested.

@matttbe
matttbe merged commit 8e1b9cd into linux-netdev:main Nov 6, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant