From: Brian Masney <masneyb@kernel.org>
To: "Kernel.org Tools" <tools@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jerome Brunet <jbrunet@baylibre.com>,
Brian Masney <masneyb@kernel.org>
Subject: [PATCH b4 0/4] review-tui: add support for setting the delegate in patchwork
Date: Wed, 14 Oct 2026 20:03:37 -0400 [thread overview]
Message-ID: <20261014-pw-delegate-v1-0-a393ae92152a@kernel.org> (raw)
Here's a series that adds support for setting the delegate in patchwork
via the review-tui.
Signed-off-by: Brian Masney <masneyb@kernel.org>
---
Brian Masney (4):
review-tui: show why a Patchwork update failed
review-tui: let ApplyStateModal update other patch fields
review: add pw_fetch_maintainers()
review-tui: change the Patchwork delegate from the pw browser
docs/maintainer/review.rst | 6 +
src/b4/review/_review.py | 57 +++++++++
src/b4/review_tui/_modals.py | 220 ++++++++++++++++++++++++++++++++--
src/b4/review_tui/_pw_app.py | 165 ++++++++++++++++++++++++-
src/tests/test_tui_pw.py | 279 +++++++++++++++++++++++++++++++++++++++++++
5 files changed, 718 insertions(+), 9 deletions(-)
---
base-commit: 6be7c6139d7734d84afddf989fa2874935b6d85b
change-id: 20261014-pw-delegate-b185593a1837
Best regards,
--
Brian Masney <masneyb@kernel.org>
next reply other threads:[~2026-10-15 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 0:03 Brian Masney [this message]
2026-10-15 0:03 ` [PATCH b4 1/4] review-tui: show why a Patchwork update failed Brian Masney
2026-10-15 0:03 ` [PATCH b4 2/4] review-tui: let ApplyStateModal update other patch fields Brian Masney
2026-10-15 0:03 ` [PATCH b4 3/4] review: add pw_fetch_maintainers() Brian Masney
2026-10-15 0:03 ` [PATCH b4 4/4] review-tui: change the Patchwork delegate from the pw browser Brian Masney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261014-pw-delegate-v1-0-a393ae92152a@kernel.org \
--to=masneyb@kernel.org \
--cc=jbrunet@baylibre.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox