All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: Petr Vorel <pvorel@suse.cz>, Jan Kara <jack@suse.com>,
	Matthew Bobrowski <repnop@google.com>,
	Ext4 <linux-ext4@vger.kernel.org>,
	kernel@collabora.com, Khazhismel Kumykov <khazhy@google.com>,
	LTP List <ltp@lists.linux.it>
Subject: Re: [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Sat, 20 Nov 2021 12:43:58 +0200	[thread overview]
Message-ID: <CAOQ4uxg0EfxefoGZr35C5HQR2Ac7BZ_HnTCq1eipvUa=iuQRWg@mail.gmail.com> (raw)
In-Reply-To: <8735nsuepi.fsf@collabora.com>

> >> A proper manpage description is also available on the respective mailing
> >> list, or in the branch below:
> >>
> >>     https://gitlab.collabora.com/krisman/man-pages.git -b fan-fs-error
> >>
> >> Please, let me know your thoughts.
> >>
> >
> > Gabriel,
> >
> > Can you please push these v4 patches to your gitlab tree?
>
> Hi Amir,
>
> I have pushed v4 to :
>
> https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4
>

Thanks. I've based my fan_rename ltp branch on this.
I would like to do the same for the man-page update branch.
However, Matthew's man page updates for v5.15 are conflicting
with your changes, so after Matthew posts v2 of his man page patch,
please rebase your changes on top of his branch.

Ideally, you could have waited until Matthew's changes are merged
upstream, like you did for ltp before rebasing, but man-pages maintainers
are quite behind on merging updates, so we will need to collaborate
between us in the meanwhile.

Thanks,
Amir.

WARNING: multiple messages have this Message-ID (diff)
From: Amir Goldstein <amir73il@gmail.com>
To: Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: kernel@collabora.com, Matthew Bobrowski <repnop@google.com>,
	Khazhismel Kumykov <khazhy@google.com>, Jan Kara <jack@suse.com>,
	Ext4 <linux-ext4@vger.kernel.org>, LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event
Date: Sat, 20 Nov 2021 12:43:58 +0200	[thread overview]
Message-ID: <CAOQ4uxg0EfxefoGZr35C5HQR2Ac7BZ_HnTCq1eipvUa=iuQRWg@mail.gmail.com> (raw)
In-Reply-To: <8735nsuepi.fsf@collabora.com>

> >> A proper manpage description is also available on the respective mailing
> >> list, or in the branch below:
> >>
> >>     https://gitlab.collabora.com/krisman/man-pages.git -b fan-fs-error
> >>
> >> Please, let me know your thoughts.
> >>
> >
> > Gabriel,
> >
> > Can you please push these v4 patches to your gitlab tree?
>
> Hi Amir,
>
> I have pushed v4 to :
>
> https://gitlab.collabora.com/krisman/ltp.git -b fan-fs-error_v4
>

Thanks. I've based my fan_rename ltp branch on this.
I would like to do the same for the man-page update branch.
However, Matthew's man page updates for v5.15 are conflicting
with your changes, so after Matthew posts v2 of his man page patch,
please rebase your changes on top of his branch.

Ideally, you could have waited until Matthew's changes are merged
upstream, like you did for ltp before rebasing, but man-pages maintainers
are quite behind on merging updates, so we will need to collaborate
between us in the meanwhile.

Thanks,
Amir.

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

  reply	other threads:[~2021-11-20 10:44 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 23:57 [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Gabriel Krisman Bertazi
2021-11-18 23:57 ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 1/9] syscalls: fanotify: Add macro to require specific mark types Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 2/9] syscalls: fanotify: Add macro to require specific events Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 3/9] syscalls/fanotify22: Introduce FAN_FS_ERROR test Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 4/9] syscalls/fanotify22: Validate the generic error info Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-19  5:38   ` Amir Goldstein
2021-11-19  5:38     ` [LTP] " Amir Goldstein
2021-11-19 19:29     ` Petr Vorel
2021-11-19 19:29       ` [LTP] " Petr Vorel
2021-11-19 22:39       ` Petr Vorel
2021-11-19 22:39         ` [LTP] " Petr Vorel
2021-11-18 23:57 ` [PATCH v4 5/9] syscalls/fanotify22: Validate incoming FID in FAN_FS_ERROR Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 6/9] syscalls/fanotify22: Support submission of debugfs commands Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 7/9] syscalls/fanotify22: Create a corrupted file Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 8/9] syscalls/fanotify22: Test file event with broken inode Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-18 23:57 ` [PATCH v4 9/9] syscalls/fanotify22: Test capture of multiple errors Gabriel Krisman Bertazi
2021-11-18 23:57   ` [LTP] " Gabriel Krisman Bertazi
2021-11-19  5:48 ` [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Amir Goldstein
2021-11-19  5:48   ` [LTP] " Amir Goldstein
2021-11-19 19:29   ` Gabriel Krisman Bertazi
2021-11-19 19:29     ` [LTP] " Gabriel Krisman Bertazi
2021-11-20 10:43     ` Amir Goldstein [this message]
2021-11-20 10:43       ` Amir Goldstein
2021-11-22  7:47     ` Petr Vorel
2021-11-22  7:47       ` [LTP] " Petr Vorel
2021-11-22 17:35       ` Gabriel Krisman Bertazi
2021-11-22 17:35         ` [LTP] " Gabriel Krisman Bertazi
2021-11-22 21:09         ` Petr Vorel
2021-11-22 21:09           ` [LTP] " Petr Vorel
2021-11-24 10:39       ` Petr Vorel
2021-11-24 10:39         ` Petr Vorel
2021-12-20 11:48         ` Amir Goldstein
2021-12-20 11:48           ` Amir Goldstein
2021-12-20 18:07           ` Petr Vorel
2021-12-20 18:07             ` Petr Vorel
2022-01-10 15:16 ` Petr Vorel
2022-01-10 15:16   ` [LTP] " Petr Vorel
2022-02-02 13:49   ` Amir Goldstein
2022-02-02 13:49     ` [LTP] " Amir Goldstein
2022-02-02 14:10     ` Jan Stancek
2022-02-02 14:10       ` Jan Stancek
2022-02-02 16:45       ` Gabriel Krisman Bertazi
2022-02-02 16:45         ` Gabriel Krisman Bertazi
2022-02-02 14:22     ` Petr Vorel
2022-02-02 14:22       ` [LTP] " Petr Vorel
2022-02-02 16:13       ` Cyril Hrubis
2022-02-02 16:13         ` Cyril Hrubis
2022-02-02 16:57         ` Petr Vorel
2022-02-02 16:57           ` Petr Vorel

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='CAOQ4uxg0EfxefoGZr35C5HQR2Ac7BZ_HnTCq1eipvUa=iuQRWg@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=jack@suse.com \
    --cc=kernel@collabora.com \
    --cc=khazhy@google.com \
    --cc=krisman@collabora.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=repnop@google.com \
    /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.