From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Liu Jian <liujian56@huawei.com>,
ltp@lists.linux.it, Ricardo Branco <rbranco@suse.de>,
Martin Doucha <martin.doucha@suse.com>
Subject: Re: [LTP] LTP release preprations
Date: Fri, 16 Jan 2026 08:20:20 +0100 [thread overview]
Message-ID: <20260116072020.GB556902@pevik> (raw)
In-Reply-To: <aWjZX0fsrTJMqq49@yuki.lan>
Hi Cyril, all,
> Hi!
> It's about we start to prepare for the January release. We have roughly
> a week for getting in all patches that should go in. So if there is
> anything that should be reviewed please point it out ASAP.
> As for me I'm going to (hopefully) finalize the ground rules patch and
> send another version today.
I plan to merge today Martin's fix for lio_listio/2-1.c:
https://lore.kernel.org/ltp/20260115171847.28091-1-mdoucha@suse.cz/
I hope we could merge userfaultfd rewrite:
https://github.com/linux-test-project/ltp/pull/1280
Hopefully v7 "new cmd support option for needs_cmds" is ready now:
https://lore.kernel.org/ltp/20260109061716.20258-1-wegao@suse.com/
ioctl_pidfd02-06: Add CONFIG_USER_NS and CONFIG_PID_NS to needs_kconfigs
https://patchwork.ozlabs.org/project/ltp/patch/20251209211629.95436-1-terry.tritton@linaro.org/
(I somehow agree with Jan that sometimes just check /proc or /sys path is better
than imply kconfig, but majority agreed to use .needs_kconfigs).
Maybe fix clone10.c on 32 bit, if we find a root cause. This is just an
investigation:
https://lore.kernel.org/ltp/aWmqFAzdtsR0t5aJ@autotest-wegao.qe.prg2.suse.org/
We got no further response for some RPC fix, I'm not sure if it's ready:
https://lore.kernel.org/ltp/20260112015047.2184003-1-liujian56@huawei.com/
If we have time:
tst_filesystems01.c: Add test for .filesystems
https://patchwork.ozlabs.org/project/ltp/list/?series=481881&state=*
checkpatch.pl update
https://patchwork.ozlabs.org/project/ltp/list/?series=487179&state=*
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-16 7:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 12:11 [LTP] LTP release preprations Cyril Hrubis
2026-01-15 12:53 ` Li Wang via ltp
2026-01-15 13:52 ` Cyril Hrubis
2026-01-16 1:45 ` Li Wang via ltp
2026-01-16 7:20 ` Petr Vorel [this message]
2026-01-22 10:38 ` Jan Stancek via ltp
2026-01-22 11:26 ` Li Wang via ltp
2026-01-16 8:18 ` Andrea Cervesato via ltp
2026-01-22 8:53 ` Petr Vorel
2026-01-22 12:33 ` Martin Doucha
2026-01-26 8:44 ` Andrea Cervesato via ltp
2026-01-27 13:06 ` Cyril Hrubis
2026-01-27 13:25 ` Petr Vorel
2026-01-28 1:59 ` Li Wang via ltp
2026-01-28 7:21 ` Petr Vorel
2026-01-28 0:57 ` Li Wang via ltp
2026-01-28 10:52 ` Martin Doucha
2026-01-28 11:24 ` Ricardo Branco
2026-01-30 9:51 ` Cyril Hrubis
2026-01-28 9:13 ` Andrea Cervesato via ltp
2026-01-28 9:54 ` Li Wang 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=20260116072020.GB556902@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=liujian56@huawei.com \
--cc=ltp@lists.linux.it \
--cc=martin.doucha@suse.com \
--cc=rbranco@suse.de \
/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