All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Jan Kara <jack@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/4] fanotify03: Add test cases for permission events on children
Date: Thu, 13 Feb 2025 08:54:55 +0100	[thread overview]
Message-ID: <20250213075455.GA2148266@pevik> (raw)
In-Reply-To: <boqw2unsm67yetv42vrn4q2d4xsfwxhys5fdfjsei7k526ltmu@zkkhjvfj3bvj>

Hi Amir, Jan,
...
> > > You are right.
> > > I was "backported" from the pre-content test.
> > > The two else statements can be removed in this patch.

> > FYI I'm going to merge with the diff below (discussed change).

> > Jan, may I add your RBT?

> Yes. Feel free to add:

> Reviewed-by: Jan Kara <jack@suse.cz>

Thanks, merged with the change above.

Kind regards,
Petr

> 								Honza

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

  reply	other threads:[~2025-02-13  7:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 15:13 [LTP] [PATCH 0/4] New tests for fanotify pre-content events Amir Goldstein
2025-02-10 15:13 ` [LTP] [PATCH 1/4] fanotify14: Test invalid init flags with permission and " Amir Goldstein
2025-02-10 15:19   ` Jan Kara
2025-02-11 17:55     ` Petr Vorel
2025-02-10 15:13 ` [LTP] [PATCH 2/4] fanotify03: Add test cases for permission events on children Amir Goldstein
2025-02-10 15:24   ` Jan Kara
2025-02-10 16:55     ` Amir Goldstein
2025-02-11 17:56       ` Petr Vorel
2025-02-12 12:35         ` Jan Kara
2025-02-13  7:54           ` Petr Vorel [this message]
2025-02-10 15:13 ` [LTP] [PATCH 3/4] fanotify24: Add test for FAN_PRE_ACCESS and FAN_DENY_ERRNO Amir Goldstein
2025-02-10 15:43   ` Jan Kara
2025-02-10 17:06     ` Amir Goldstein
2025-02-11 19:09       ` Petr Vorel
2025-02-11 20:12         ` Amir Goldstein
2025-02-20 20:42           ` Petr Vorel
2025-02-21 13:26             ` Petr Vorel
2025-02-21 13:37               ` Amir Goldstein
2025-02-28 20:11   ` Heiko Carstens
2025-02-10 15:13 ` [LTP] [PATCH 4/4] fanotify24: Test open for write of executable files with pre-content watch Amir Goldstein
2025-02-10 15:59   ` Jan Kara

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=20250213075455.GA2148266@pevik \
    --to=pvorel@suse.cz \
    --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.