Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>,
	Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>,
	Edvard Conrad <edvard@tuta.io>
Subject: Re: [LTP] [PATCH] syscalls/fanotify26: Move from staging to syscalls
Date: Thu, 5 Nov 2026 19:11:14 +0100	[thread overview]
Message-ID: <20261105181114.GA523231@pevik> (raw)
In-Reply-To: <20261103200333.GA154873@pevik>

Hi all,

> 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.

OK, v7.4-rc1 is out and Amir and Cyril pointed out this is a regression test for
a real (old) bug not a new feature.  I rebased the patch and merged.

Thanks!

Kind regards,
Petr

> Kind regards,
> Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2026-11-05 18:11 UTC|newest]

Thread overview: 7+ 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
2026-11-05 18:11       ` 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=20261105181114.GA523231@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox