From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
Edvard Conrad <edvard@tuta.io>,
"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] syscalls/fanotify26: Move from staging to syscalls
Date: Tue, 3 Nov 2026 21:03:33 +0100 [thread overview]
Message-ID: <20261103200333.GA154873@pevik> (raw)
In-Reply-To: <auoPxzIaqjk7qUma@yuki.lan>
Hi all,
> Hi!
> > On the other hand, Petr, this is not a new feature, it is a real bug fix.
> > Are we holding off on running tests on newly found bugs
> > until those bugs are fixed upstream?
> I do not think that we need to hold off tests for bugs. The rule we have
> has been introduced since newly added kernel ABIs are subject to change
> in the rc phases.
Yes that's true, this is a different case. Anyway, if all distro users test with
LTP releases (they are using master branch), I'm ok to merge before fix is
merged and it's hash added to the test.
We are using LTP master branch for testing SLES in development and openSUSE
Tumbleweed, filtering these errors involves some work, but that's ok.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-11-03 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 17:31 [LTP] [PATCH] syscalls/fanotify26: Move from staging to syscalls Edvard Conrad via ltp
2026-10-31 19:37 ` [LTP] " linuxtestproject.agent
2026-11-01 16:46 ` [LTP] [PATCH] " Amir Goldstein
2026-11-02 10:57 ` Edvard Conrad via ltp
2026-11-03 16:45 ` Cyril Hrubis
2026-11-03 20:03 ` Petr Vorel [this message]
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=20261103200333.GA154873@pevik \
--to=pvorel@suse.cz \
--cc=amir73il@gmail.com \
--cc=chrubis@suse.cz \
--cc=edvard@tuta.io \
--cc=jack@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.