From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/8] fanotify tests for v5.13
Date: Mon, 22 Mar 2021 20:07:57 +0100 [thread overview]
Message-ID: <YFjrDTAePFgXZR6b@pevik> (raw)
In-Reply-To: <CAOQ4uxjWTKncGxcOfT9XJ8REXZt9fdB7QsWRT74hUrB8mkNg-Q@mail.gmail.com>
Hi Amir,
> > > Whatever you think is best for your project users.
> > > If you want to document the commits that added the features, I suggest
> > > that you wait until those commits hit master (next cycle).
> > > These are the relevant commit subjects:
> > > fanotify: configurable limits via sysfs
> > > fanotify: support limited functionality for unprivileged users
> > Thanks a lot!
> > IMHO being in next tree should be ok (commits hashes should be kept).
> There is no such guarantee, certainly not so far from the v5.13 merge
> window, so I advise against including the commit ids at this point.
> The commit subject is descriptive enough IMO and you can add commit
> ids later on if you think it is necessary.
OK, make sense to wait with commit hashes. I'll merge it tomorrow as is (with
that formatting and fixing old kernel changes I posted earlier).
Kind regards,
Petr
next prev parent reply other threads:[~2021-03-22 19:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 13:11 [LTP] [PATCH 0/8] fanotify tests for v5.13 Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 1/8] syscalls/fanotify05: Fix test output when not getting overflow Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 2/8] syscalls/fanotify05: Verify events are received by queue order Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 3/8] syscalls/fanotify05: Verify getting a single overflow event Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 4/8] syscalls/fanotify05: Add a test case for unlimited queue Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 5/8] syscalls/fanotify05: adjust test to tunable max_queued_events Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 6/8] syscalls/fanotify: New test for fanotify user limits Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 7/8] syscalls/fanotify: New test to validate unprivileged user permissions Amir Goldstein
2021-03-18 13:11 ` [LTP] [PATCH 8/8] syscalls/fanotify: New test to validate unprivileged listener events Amir Goldstein
2021-03-19 13:04 ` [LTP] [PATCH 0/8] fanotify tests for v5.13 Petr Vorel
2021-03-19 13:54 ` Amir Goldstein
2021-03-21 20:13 ` Petr Vorel
2021-03-22 18:42 ` Amir Goldstein
2021-03-22 19:07 ` Petr Vorel [this message]
2021-03-23 6:36 ` 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=YFjrDTAePFgXZR6b@pevik \
--to=pvorel@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