From: linuxtestproject.agent@gmail.com
To: Edvard Conrad <edvard@tuta.io>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] syscalls/fanotify26: Move from staging to syscalls
Date: Sat, 31 Oct 2026 19:37:46 +0000 [thread overview]
Message-ID: <20261031193746.6322-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <P5I00QE--F-9@tuta.io>
Hi Edvard,
On Sat Oct 31 18:31:21 2026 +0100, Edvard Conrad <edvard@tuta.io> wrote:
> syscalls/fanotify26: Move from staging to syscalls
> diff --git a/runtest/staging b/runtest/staging
> index 2ce76b119..ef1cdea15 100644
> --- a/runtest/staging
> +++ b/runtest/staging
> @@ -1,2 +1 @@
> # Tests for features that are not yet in the stable kernel ABI
> -fanotify26 fanotify26
> diff --git a/runtest/syscalls b/runtest/syscalls
> index ff3de1b15..23d3e21ef 100644
> --- a/runtest/syscalls
> +++ b/runtest/syscalls
> @@ -703,6 +703,7 @@ fanotify22 fanotify22
> fanotify23 fanotify23
> fanotify24 fanotify24
> fanotify25 fanotify25
> +fanotify26 fanotify26
Kernel commit c3d355f427ce targets v7.4-rc1, while the latest stable
kernel release is v7.3. Tests that depend on kernel changes not yet in a
finalized mainline release must remain in runtest/staging until v7.4 is
released. Keep fanotify26 in runtest/staging until v7.4 is out, or split
the linux-git tag addition into its own patch if needed now.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-10-31 19:38 UTC|newest]
Thread overview: 2+ 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 ` linuxtestproject.agent [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=20261031193746.6322-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=edvard@tuta.io \
--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.