From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] Switch to patchwork.kernel.org
Date: Mon, 3 Aug 2026 11:44:45 +0200 [thread overview]
Message-ID: <20260803094445.GA217746@pevik> (raw)
In-Reply-To: <6a705e29.c69142e7.53fee.4a71@mx.google.com>
Hi Andrea,
> Hi Petr,
> > to patchwork.kernel.org. FYI we already have 18 patches on it, AI review is
> > there as well.
> Unfortunately AI review doesn't work there at the moment, I'm waiting for
> the LTP CI user set inside the new patchwork instance. But for now, we can
> backup this with my personal token, if needed.
Good catch, thanks! Although AI reviews are posted to both instances (they both
get mails from LTP ML), the review status does not work. That's due LTP CI user
not being part of LTP maintainers on patchwork.kernel.org [1] (as it is on the
old instance [2]) that should be solved soon. Please let me know if there is
something else missing.
FYI new instance also have only REST API enabled, the deprecated XML-RPC API is
disabled. Fortunately Andrea's ci/tools/patchwork.sh script uses the REST API :).
If somebody uses pwclient, it requires ~/.pwclientrc modification:
-url = https://patchwork.ozlabs.org/xmlrpc/
+url = https://patchwork.kernel.org/api/
+backend = rest
I also wonder if (once we switch) should send an announcement to LTP ML.
And (how ironically) atm patchwork.kernel.org respond really slowly for me,
patchwork.ozlabs.org does :). I suppose that should be just temporarily.
Kind regards,
Petr
[1] https://patchwork.kernel.org/project/ltp/
[2] https://patchwork.ozlabs.org/project/ltp/
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-03 9:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:45 [LTP] [PATCH 1/1] Switch to patchwork.kernel.org Petr Vorel
2026-07-31 6:14 ` [LTP] " linuxtestproject.agent
2026-07-31 7:25 ` [LTP] [PATCH 1/1] " Avinesh Kumar via ltp
2026-07-31 7:43 ` Andrea Cervesato via ltp
2026-08-03 9:13 ` Petr Vorel
2026-08-03 9:22 ` Cyril Hrubis
2026-08-03 9:28 ` Andrea Cervesato via ltp
2026-08-03 9:44 ` Li Wang
2026-08-03 10:24 ` Petr Vorel
2026-08-03 10:34 ` Andrea Cervesato via ltp
2026-08-03 11:06 ` Petr Vorel
2026-08-03 10:24 ` Cyril Hrubis
2026-08-03 10:26 ` Petr Vorel
2026-08-03 10:33 ` Petr Vorel
2026-08-03 9:23 ` Andrea Cervesato via ltp
2026-08-03 9:44 ` Petr Vorel [this message]
2026-08-03 10:14 ` Andrea Cervesato via ltp
2026-08-03 9:29 ` Jan Stancek via ltp
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=20260803094445.GA217746@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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