From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-api@vger.kernel.org, Steve Grubb <sgrubb@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM
Date: Thu, 18 Oct 2018 23:12:46 +1100 [thread overview]
Message-ID: <20181018121245.GC3620@workstation> (raw)
In-Reply-To: <CAOQ4uxi=raNzRzUmv6MY8-SrWfmop3pLAidOENqWH2G-1Ttz=A@mail.gmail.com>
On Thu, Oct 18, 2018 at 01:07:37PM +0300, Amir Goldstein wrote:
> On Wed, Oct 17, 2018 at 12:04 PM Matthew Bobrowski
> <mbobrowski@mbobrowski.org> wrote:
> >
> > Please note that all modifications here are based on the changes Amir has
> > made around deprecating some of the previously exposed UAPI constants. The
> > branch which my changes are based on can be found here:
> >
> > https://github.com/amir73il/linux/tree/fanotify_api-v3
> >
>
> Please note that this branch is slightly outdated.
> When testing you should rebase your patches on top of
> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git fsnotify
Perfect, and will do. Thanks for sending that through.
> I don't think that you need to re-post unless Jan wants a re-post of patch #3
> because there shouldn't be any rebase conflicts.
Yeah, that's what I mentioned within my previous email. I mean, the
ammendments to these files are minimal, so I don't really know whether I
need to submit a completely new patch series through for each update after
a review? Happy to re-post, if required.
--
Matthew Bobrowski <mbobrowski@mbobrowski.org>
prev parent reply other threads:[~2018-10-18 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 9:04 [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM Matthew Bobrowski
2018-10-17 9:05 ` [PATCH v5 1/3] fanotify: introduce new event type FAN_OPEN_EXEC Matthew Bobrowski
2018-10-17 9:05 ` [PATCH v5 2/3] fanotify: return only user requested event types in event mask Matthew Bobrowski
2018-10-17 9:05 ` [PATCH v5 3/3] fanotify: introduce new event type FAN_OPEN_EXEC_PERM Matthew Bobrowski
2018-10-18 9:26 ` Jan Kara
2018-10-18 11:55 ` Matthew Bobrowski
2018-10-18 9:28 ` [PATCH v5 0/3] fanotify: introduce new event types FAN_OPEN_EXEC and FAN_OPEN_EXEC_PERM Jan Kara
2018-10-18 12:06 ` Matthew Bobrowski
2018-10-18 12:48 ` Jan Kara
2018-10-24 4:52 ` Matthew Bobrowski
2018-10-18 10:07 ` Amir Goldstein
2018-10-18 12:12 ` Matthew Bobrowski [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=20181018121245.GC3620@workstation \
--to=mbobrowski@mbobrowski.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sgrubb@redhat.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.