From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP release preprations
Date: Tue, 27 Jan 2026 14:25:14 +0100 [thread overview]
Message-ID: <20260127132514.GB146899@pevik> (raw)
In-Reply-To: <aXi4P0YdKx5rFZ8C@yuki.lan>
> Hi!
> Are there any other fixes that should be considered before the git is
> tagged?
* 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/
(Or I can prepare an alternative fix to do a runtime check, I also plan to send
a patch with formalising the rules)
* tst_net.sh fixes would be nice to get merged:
https://patchwork.ozlabs.org/project/ltp/list/?series=489902&state=*
https://lore.kernel.org/ltp/20260127131427.146592-1-pvorel@suse.cz/
https://lore.kernel.org/ltp/20260127131427.146592-2-pvorel@suse.cz/
https://patchwork.ozlabs.org/project/ltp/list/?series=489469&state=*
It should be safe to merge these:
* v5 tst_filesystems01.c: Add test for .filesystems
https://patchwork.ozlabs.org/project/ltp/list/?series=489469&state=*
* checkpatch.pl enhancement to check for typos
https://patchwork.ozlabs.org/project/ltp/list/?series=487179&state=*
(I did not merged it as I hoped for a discussion what else to enable for
warnings, but that could be done as a separate effort after the release).
FYI I dared to merge IMA fix:
https://github.com/linux-test-project/ltp/commit/1ba58805ea5466df5202ff2e7b5b3d0cd5c81c37
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-27 13:25 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
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 [this message]
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=20260127132514.GB146899@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.